How does Cxense DMP work with my Qualifio campaigns?

Tabata Vossen -

The Qualifio - Cxense DMP integration is currently a Beta Feature. You must contact your Qualifio Expert to enable this integration and define the script to be integrated. We can give you early access, even though the work isn't 100% finished and there might still be bugs or weaknesses.

What does the Cxense DMP integration do?

This integration adds your Cxense script in your campaigns.

Once integrated, the Cxense script will be executed as soon as the first page of your campaign is displayed.

Configuration

Visit Settings → Integrations & Partners, and make sure Cxense DMP is enabled:

To configure the integration, click Configure.

Specify the Cxense site ID

Specify your Site ID that you received from Cxense in there:

Screenshot_2019-09-02_at_10.46.39.png

If you're not sure where to find this information, please coordinate with your Cxense implementation manager.

You may enter a default Site ID for your whole account, or a unique Site ID per website. We will use the most accurate ID possible, so the Default ID if not found at the website level. In other words, if you don’t provide an ID by website, we will use the Default ID.

Update data mapping

Qualifio fields need to be mapped to Cxense in order to have them available for your DMP.

To define a data mapping for a new campaign, in your Qualifio account, select the Cxense logo next to your campaign title:

Screenshot_2019-09-02_at_11.01.51.png

Define Cxense "origin" and "persisted Query ID"

Once you have completed your Site ID, you can define your event attributes in your Qualifio campaigns:

Screenshot_2019-09-02_at_11.03.42.png

If you're not sure where to find this information, please coordinate with your Cxense implementation manager.

Define Cxense data mapping

The data mapping is an essential piece of your DMP integration. It is necessary so that we can send your data to Cxense.

In order to create a data mapping for your campaign, you will be presented with a field for each

  • question
  • form field
  • qualification question
  • opt-in
  • coregistration
  • campaign theme
  • profile, in case you have a personality test campaign.

You must provide a key for each field you want to collect in Cxense, and then you can specify the different rules and values that will be sent to the DMP.

The following is an example of a data mapping screen:

Screenshot_2019-09-02_at_14.54.48.png

For each question and form field, you can define

  • Keys give information about the desired destination of the data. They must match a parameter that is supported by Cxense.
  • Rules state how we should treat the data related to a specific question or form field.
  • Values determine what data needs to be sent to your DMP.

Questions

Screenshot_2019-09-02_at_15.01.06.png

  • Key was specified (e.g. celeb-netflix).
  • Rule was selected – we will send the label of the answer chosen by the participant (e.g. Robert Pattinson).
  • No values are required, since we already know what data will be sent to the DMP.

Screenshot_2019-09-02_at_15.02.30.png

  • Key was specified (e.g. diameter-earth).
  • Rule was selected – we will send a specific value to the DMP (e.g. "11" if the participant selected "11,000 km" as answer).
  • Values to be sent were entered – for each answer to this question, we needed to know what specific value we have to return.

NOTE

If an answer doesn't have a value, the mapping is not applied. No data will be sent for this specific answer.

Screenshot_2019-09-02_at_15.07.06.png

  • Key was specified (e.g. math-apples).
  • In this case, as we're dealing with an open-ended question, we can either return the answer that was entered by the participant.

Form fields

Screenshot_2019-09-02_at_15.13.47.png

  • A key was specified for each form field. For example, here we mapped the field First name to a field named first-name. In some cases, the field names might be the same in both systems, but it is not always so.
  • The selected rule is "Return answer filled" – we will send the participant's full entry to each of these fields to your DMP.

While the examples above should cover most of your mapping needs, you can optionally choose for us to return a custom (static) value that you specify:

Screenshot_2019-09-02_at_15.08.54.png

This is convenient for static values that don't change from one participation to another: when this rule is applied, we send the same unique value for all participations –whatever the participant's actual answer was.

Opt-ins

Screenshot_2019-09-02_at_15.16.18.png

Only one rule can be applied to opt-ins: we will return a unique value, which will only be sent in case the participant agrees to your opt-in. In the example above, we will send "yes" if the participant subscribed to your newsletter. In case they do not, we will not send anything.

Only when you save your mapping will the Cxense DMP integration be active for this campaign.

Limitations of the Beta version

  • Matrix questions and upload fields are not supported at this time.
  • There is no template management: the data mapping is to be done for each campaign for which you want to enable the integration.
  • It is not possible to use different data mappings for the same campaign. If your campaign is to be published on 2 channels and you want a different mapping for each channel, you can however duplicate your campaign to have one channel per campaign. You can then make 2 different mappings.
  • Campaign Themes are not automatically transferred: the value sent to the DMP is not inherited from the configuration made in Qualifio.
Powered by Zendesk