Skip to main content

Native Destinations

Kevel Audience integrates with the following catalog of third-party platforms:

Kevel UserDB​

Connect Kevel Audience with Kevel's Ad Server user database, UserDB, in order to set users' custom properties. To set up the destination you need your API key and your network ID. For the latter, you can obtain it in the Kevel Ad Server dashboard, as shown in the figure below:

Kevel UserDB network ID location

Any existing custom properties are replaced for that user on each user activation to Kevel's UserDB. Other UserDB properties, like interests, will not be impacted by activations from Audience.

Pushing or removing segments from the UserDB destination won't affect targeting rules in the Kevel's Ad Server campaigns.

Kevel UserDB destination creation

It is also possible to have access to the HTTP requests a given configuration will result in, with the "See request(s)" button on the destination form.

Kevel UserDB see HTTP request

Adestra​

Make the most of your user data with email and marketing automation supercharged by Kevel Audience's machine-learning capabilities.

Adform​

Serve personalized display ads to your machine learning-powered audiences via integration between Adform and Kevel Audience.

Criteo​

Connect with Kevel Audience to make the most out of Criteo’s advertising technology solutions with your machine learning tailored audiences.

E-goi​

E-goi integration allows you to attach Tags to existing E-goi Contacts according to segmentation rules defined within the CDP.

User Data Import from an E-goi Source​

To be able to attach tags to E-goi contacts, the CDP needs to have access to their E-goi identifier first, so this functionality requires you to first configure a User data import.

To make sure that the CDP is synchronized with the E-goi contact list and new users have the opportunity to be activated once the destination is enabled, you should also configure the import to happen on schedule, and, thus, keep the contact list and the CDP data in sync.

Enabling Activations​

Once you are confident you are already importing the Contact List data into your CDP, you can enable a destination and use the segmentation capabilities to attach tags to your contacts on E-goi side.

Go ahead and create a new destination of type E-goi - Contact Tags. Just as with the user import you need to provide this destination with an API key and List ID. The difference for the API key is that the destination requires different permissions.

The set of required permissions for the API key on this destination are the following:

  • Attach tag to contact
  • Detach tag from contact
  • Get all contacts
  • Get all tags
  • Create tag
  • Get my account info

The List ID should be the same you configured for the user import.

After those details are filled in, you should specify the Data mapping you want to create between E-goi Tags and CDP segments your users may or not belong to.

E-goi Contacts destination data mapping

For every pair tag/segment you specify, an activated user of this destination will:

  • have the corresponding tag attached if it belongs to the CDP segment
  • have the corresponding tag detached if it does not belong to the CDP segment.

Note that changing or deleting mappings, as well as deleting the destination, will not remove tags that were created or attached to contacts on the E-goi platform.

Finally, you should also define a trigger for this destination. Schedule triggers will ensure your users continue to be activated even when they do not interact with your website.

Facebook Conversions API​

Facebook Conversions API activations allow you to send events captured with Kevel Audience tracking pixel directly to Facebook using their dedicated API. This allows improving on the data tracked by the Facebook pixel by complementing it with information only available on Kevel Audience (e.g., extra user ids). It also enables tracking events in scenarios where the Facebook pixel can't be used (e.g., due to the lack of support for third-party cookies).

These activations differ from the rest of the activations in the sense that they don't allow pushing individual user attributes to third-party platforms, but rather user events.

Collecting Events​

In order to send events to Facebook, you need to first start sending Facebook tracking information within your tracking events. To do so, all event type schemas support the facebookConversionTracking field, where you can customize the event_name and custom_data with the same data you would use when using the facebook pixel. For an example of what that schema looks like, you can check the pageView event type documentation.

This means that if you have a JavaScript tag using the Facebook pixel that would include a call such as the following:

fbq("track", "Purchase", {currency: "USD", value: 30.00});

You would mimic the same Facebook tracking event using the Kevel Audience tag with:

pcdp("event", "track", {
  "facebookConversionTracking": {
    "event_name": "Purchase",
    "custom_data": {
      "currency": "USD",
      "value": 30
    }
  }
  // extra event data should be included here
});

Enabling Activations​

Once you're sending Facebook events embedded within your Kevel Audience events, you need to create a destination so that events are properly pushed to Facebook. To do so, create a destination of type Facebook - Conversions API, configuring it with the proper pixel ID and system access token, which you should generate directly from Facebook. After a destination being set up and enabled, tracking events should start being pushed to Facebook as soon as they arrive on the CDP.

Sending Additional User Identifiers​

This destination will send the values from the _fbp and _fbc cookies as well as the user-agent as user identifiers, when available on the request. Additional optional IDs, such as email or phone number hashes, increase the match rate for the event. We recommend enabling all the supported IDs to maximize the usefulness of the integration.

You can also use one external ID to identify the user on Facebook. With this strategy, you can choose an ID type to use for the external ID. Keep in mind that the selected external IDs must be provided to Facebook on other channels so that the user can be recognized using this ID, as described in https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/external-id/.

note

Having this destination setup to send Facebook Browser ID and/or Facebook Browser ID invalidates the option to Skip activation if data to activate hasn't changed since last activation

Deduplicating Events​

If you're using both Facebook pixel and the Kevel Audience tag you might happen to send the same event to Facebook twice. In order to avoid Facebook considering the duplicated event as two different events, you should set up a deduplication process. To do that, you should send the same event name and event id in both the Facebook pixel and the Kevel Audience tag.

Building on the previous example, you should start including an eventID on calls to Facebook pixel:

fbq("track", "Purchase", {currency: "USD", value: 30.00}, {eventID: my_event_id});

And send the same event id when using the Kevel Audience tag:

pcdp("event", "track", {
  "facebookConversionTracking": {
    "event_name": "Purchase",
    "event_id": my_event_id,
    "custom_data": {
      "currency": "USD",
      "value": 30
    }
  }
  // extra event data should be included here
});

Filtering by Pixel ID​

You might want to configure different destinations for different pixel ids. In order to do so, you can send an optional pixel_id property on facebookConversionTracking that indicates the pixel ID the event should be associated with:

pcdp("event", "track", {
  "facebookConversionTracking": {
    "event_name": "Purchase",
    "pixel_id": my_pixel_id,
    "custom_data": {
      "currency": "USD",
      "value": 30
    }
  }
  // extra event data should be included here
});

Once you're doing that, you can enable the "Filter by Facebook Pixel ID" option in your destination so that only events whose pixel ID matches the pixel ID of the destination are pushed via that destination.

Facebook Custom Audiences​

Activate email and phone number IDs to Facebook Custom Audiences using a server-to-server connection. Re-engage dormant clients who haven’t visited the site in a while to improve retention rates.

To connect Kevel Audience with Meta, the Meta user account used for configuring the integration must have admin permissions to the Business Manager associated with the Ads account. Personal ad accounts are not supported.

Facebook Pixel​

Reach your pre-segmented audiences on Facebook to serve relevant and timely ads to the right people at the right time.

Connect Kevel Audience and Google Ads to reach your first-party audiences in search and display campaigns. The time to process each list is out of the Kevel Audience's control and can take up to more than a day for lists with a large volume of activations.

Google Analytics​

Connect Kevel Audience and Google Analytics to incorporate your first-party audience intelligence into your e-commerce analytics.

Google Display & Video 360​

Connect Kevel Audience and Google Display & Video 360 and to deliver campaigns to your first-party audiences.

intelliAd​

Connect with intelliAd’s performance marketing suite and push your smart audiences to maximize your performance.

Klaviyo​

Configure custom properties on Klaviyo's user profiles that can be used for segmentation. If the profile does not exist on Klaviyo, it is created with the first activation, considering the email address and/or phone number available. If an user is activated with multiple IDs, such as a email address and phone number, the profiles generated on Klaviyo will not be automatically merged. This destination requires your Klaviyo's public API key.

Please note that Klaviyo's Track & Identify API can only provide feedback regarding the structure of the request. The request content is processed asynchronously. We recommend that you validade that properties are being properly set on Klaviyo's profiles after enabling the destination.

Mailchimp​

Collect data and push smart audiences to Mailchimp. Apply powerful machine learning to your email marketing with Kevel Audience.

Mailgun​

Mailgun’s out-of-the-box integrations lets you push your audiences and improve email marketing ROI with machine learning-powered segments.

MediaMath​

Push your audiences to MediaMath using its pixel and segment parameters, or S2S integration, using cookie syncing to identify MediaMath’s user cookies.

Monetate​

Integrate the data from one of the leading customer personalization platforms to enrich your user's profiles.

Pinterest​

Connect to Pinterest to reach people who are ready for your ideas and products and capitalize on that data.

Postmark​

Postmark and Kevel Audience work in tandem to make automated transactional emails even more effective with the power of machine learning.

Remintrex​

Supercharge your retargeting strategy with Remintrex powered by Kevel Audience segments and captivate visitors who’d be lost otherwise.

SendGrid​

Automatically send audiences to Sendgrid and supercharge your transactional and email marketing data with machine learning.

Sendinblue​

Go beyond Sendinblue’s dashboard by pushing your smart segments. Make the most out of your email campaigns, transactional emails, SMS messages, chat and CRM data.

Smartclip​

Smartclip offers you the possibility to offer personalized multiscreen ad experience to your audiences via integration with Kevel Audience.

SpotX​

Syncing SpotX and Kevel Audience gives valuable insight into video performance across desktop, mobile and connected devices.

Last updated on