Skip to main content

Blueshift

Overview​

The Blueshift Conversions API destination lets you authenticate to Blueshift for sending conversion events.

At this time, the destination connector’s loading/sync behavior is still in development. You can configure the destination and validate credentials, but runs will not load data yet.

Setup​

  1. In Blueshift, obtain an Event API Key that can be used with the Conversions/Event API.
  2. Identify your Blueshift base URL (for example, https://api.getblueshift.com), or the appropriate Blueshift API host for your account/region.
  3. In your workspace, create a new Reverse ETL destination and select Blueshift Conversions API.

Authentication​

This destination uses HTTP Basic Auth:

  • Username: your Event API Key
  • Password: blank

Credential validation calls:

  • GET {base_url}/api/v1/event/debug

If validation fails, confirm the base URL and that the Event API Key is active and has the required permissions.

Configuration​

FieldTypeRequiredDescription
base_urlstring✅Blueshift API base URL. The connector will append /api/v1/event/debug for credential validation. Trailing slashes are allowed.
event_api_keystring✅Blueshift Event API Key used as the Basic Auth username (password is blank).

Streams​

This destination is intended to load conversion/event records into Blueshift via the Conversions API.

Note: Loading is currently not available (the connector will error during load). Only credential validation is supported at this time.