Skip to main content

BlueConic Experiences

Send form responses to Blueshift as events, and route visitors based on their Blueshift profile.

You can send responses from BlueConic Experiences, such as sign-up form submissions, to Blueshift as events. Use these events to trigger your Blueshift campaigns and journeys. You can also route visitors through an experience based on their Blueshift profile, for example whether they're subscribed to email.

Before you begin

You need these from your Blueshift account:

  • Your Users API Key and Event API Key. BlueConic Experiences calls the first one User API Key. For more information, see API Keys.

  • Your Blueshift region: US or EU.

  • To route visitors by Email deliverable: your Email Validation Key. It's on the same API Keys page in Blueshift when email validation is turned on for your account. If there's no key yet, an admin can click Generate. To turn on email validation, contact Blueshift Support at [email protected].

Connect Blueshift in BlueConic Experiences

In BlueConic Experiences, add a Blueshift integration to your brand under Attributes > Integrations. Enter your API keys, select your Blueshift region, and make sure the integration is Active. For more information, see Manage multiple integration instances in the BlueConic Experiences help center.

Each integration maps to one Blueshift region. To send to an account in another region, add another Blueshift integration with that account's keys.

Important: An integration applies to every experience in your brand, including new ones. To stop an experience from sending to Blueshift, select it under Excluded experiences from this integration in the integration, and then click Apply.

Map form fields to Blueshift events

In the integration, add a mapping for each form field that you want to send. When you choose the Attribute, Mapping name fills in with the same name, such as first_name. In Mapping name, enter the Blueshift attribute name instead where the names differ, for example firstname.

To set the event name, add a static value named event to the mapping, set to the Blueshift event name. For accounts in the US region, you can pick the event name from the events in your Blueshift account after you enter the User API Key in the integration. If the list doesn't appear, type the event's Event Name. To find it in Blueshift, go to Customer Data > Events, open the event, and check its Properties tab. The Event Name can differ from the event's Display Name, and campaigns trigger on the Event Name.

Mappings in the Blueshift integration in BlueConic Experiences, each tagged with its event name
  • Mappings on the same screen that share an event name are sent together as one event.

  • Each mapping can have its own event name, so one integration can send different events from different steps of an experience.

Note: After you fill in a mapping, click Add mapping before you save. If you save with a mapping that isn't added, choose Add mapping & save or Go back. If that mapping is incomplete, choose Discard & save or Go back.

Important: If a campaign is triggered by an event, put all the fields mapped to that event on one screen. If they're spread across more than one screen, the event is sent once for each screen, and the campaign can send more than once.

Test before you publish

In the experience builder, click Preview, which opens the experience in a new browser tab. Then click the Test API Integration icon at the top right to see each event as it's sent, with the data it contains. For more information, see Test API integrations with the triage tool in the BlueConic Experiences help center.

Important: Test submissions send real events to your Blueshift account. They update the customer's profile and can trigger campaigns, so test with an email address that you own.

See the events in Blueshift

  1. In Blueshift, go to Customer Data > Profiles.

  2. Search for the customer, for example by email address, and open their profile.

  3. Open the Activity tab. Each event from BlueConic Experiences is listed by name and date. Select an event to see its attributes.

The Activity tab of a customer profile in Blueshift, listing identify events

Each event includes the visitor's cookie. When an event includes an email address or phone number, Blueshift merges the anonymous visitor into that customer's profile.

Events sent before the visitor was identified don't appear on the profile. To see them, go to Customer Data > Events, open the event, and open its History tab.

Route visitors by their Blueshift profile

After you add a Blueshift integration, you can route visitors by their Blueshift profile. Add a Split Traffic step to the experience, choose Blueshift Profile, and then set the condition for each branch.

The split sends each visitor down a path based on their Blueshift profile. A branch can check whether the visitor is:

  • Known in Blueshift

  • Subscribed to email

  • Subscribed to SMS

  • Email deliverable: this works only when you enter your Email Validation Key in the integration's Email Validation Key (Optional) field. Lookups for this condition use your Blueshift email validation credits.

Every split has a Default Branch. It catches every visitor who doesn't match another branch, including when the lookup fails or times out, or when the experience has no way to identify them. To send visitors that Blueshift already knows down their own path, use the Known in Blueshift condition.

Note: To identify visitors, place the split after a step that collects their email address or phone number. If you embed the experience on a page that runs the Blueshift website SDK, the visitor's Blueshift cookie is also passed into the experience.

Did this answer your question?