Skip to main content
A successful export doesn’t always mean every field landed. Blinq can show an export as successful when Salesforce rejected the record, or when Blinq left out a field the connected user can’t edit. Check the record in Salesforce, not just the export status in Blinq.
Most problems below come from a setting in Salesforce rather than in Blinq. None of them lose data: contact details and lead form answers stay in Blinq, and reach Salesforce when you re-export the contacts.

Nothing is reaching Salesforce

Use Reconnect, not Disconnect. Disconnecting keeps your Salesforce settings but deletes your field mappings, so you’d have to set them up again.
A connection can expire when:
  • it hasn’t been used for 30 days;
  • the Salesforce user who connected it is deactivated;
  • that user’s access to the Blinq app is revoked in Salesforce;
  • the same Salesforce user connects Blinq more than five times, for example across a sandbox and production. Salesforce keeps five connections per user for each app and drops the oldest.

A mapped field is blank in Salesforce

These cases leave one field empty while the rest of the record syncs.
Renaming a lead form field, or changing its answer options, doesn’t break its mapping. Deleting a field and creating a new one with the same name does: the new field needs mapping again. Reuse existing fields where you can.

Salesforce rejected the whole record

In these cases Salesforce rejects the entire record, so nothing on it is created or updated. Blinq still shows the export as successful.

Fixing restricted picklists

Every option on your Blinq dropdown needs a matching value in the Salesforce picklist it’s mapped to. Otherwise the next answer that isn’t on the list won’t sync either. This includes standard fields such as Lead Source. Your Salesforce admin can fix it in one of two ways:
  • Add the missing values. In Salesforce, go to Setup → Object Manager → Lead (or Contact) → Fields & Relationships, open the field, and under Values select New. See Salesforce’s guide to managing picklist values.
  • Make the field unrestricted. Edit the field and untick Restrict picklist to the values defined in the value set, so it accepts any value. See “Restricted Picklists” in Salesforce’s picklist guide.
Then re-export the affected contacts.

A field doesn’t appear in the Field Mapper

  • Reload the page. The Field Mapper loads your fields from Salesforce each time it opens, so a field you’ve just created appears after a reload.
  • Check field access. The Salesforce user who connected Blinq needs read and edit access to the field on their profile.
  • Check the connection. If the Field Mapper shows “We couldn’t refresh your Salesforce connection”, select Reconnect.

After you fix it: re-export

Re-export the affected contacts from Contacts → All company contacts. Blinq updates the records it already manages in Salesforce, using your current field mappings. A matching record that another source manages is left unchanged.

What to send support

If none of these explain it, email support@blinq.me with your workspace name, your Salesforce org URL, the affected email addresses, and roughly when the contacts were captured. A screenshot of the Field Mapper rows involved helps too.

Need help?

For any questions or issues, contact Blinq support or email support@blinq.me.