Integrations
Bing Ads Universal Event Tracking (UET) you can create one UET tag and place it across your website, allowing you to collect data for tracking conversion goals and targeting audiences with remarketing lists.
This is a kit-only integration that solely supports client-side data forwarding.
In order to enable mParticle’s integration with Bing, you will need your Universal Event Tracking (UET) Tag ID. Follow the steps here to create your UET tag. In the View UET tag tracking code box, your Tag ID will be shown.
At least one of the following fields is required to forward events to Bing:
mParticle maps logged events to Bing’s event structure as follows:
Bing Parameter | Description | Mapping |
---|---|---|
ec | Event Category | event.EventCategory |
ea | Event Action | Set to ‘pageLoad’ or ‘ecommerce’, if logEvent or logPurchaseEvent is called, respectively. |
el | Event Label | event.EventName |
ev | Event Value | Set to the ‘Bing.EventValue’ Custom Flag. |
gv | Goal Value (Variable Revenue) | event.ProductAction.TotalAmount (Only used if logPurchaseEvent is called). |
Microsoft uses an ad_storage
property to signify that a user has granted or denied consent to a marketer. As per their Consent Mode documentation, this value must be sent on every page load via the UET Tag.
To configure user consent forwarding under this value, a mapping should be set-up leveraging mParticle’s notion of Consent Purposes. To learn more about handling user consent within mParticle’s platform, see the following docs: Data Privacy Controls.
Once a Consent Purpose is set up, user consent information can be associated with it in subsequent Event Batches. The Consent Purpose data mapping can then be configured for downstream forwarding via the User Consent Data Mapping connection setting.
In the absence of a user-defined consent value for the ad_storage
field via the Consent Purpose mapping, a default value can be optionally configured via a separate drop-down setting for each consent type. When no user consent is provided, the default status is used, if specified. If omitted, we will provide a status of granted
, as per Microsoft’s Recommendation.
Caution: It is recommended that in the long term, you set up user-specified consent through the Consent Purpose mapping, such that the user consent is correctly forwarded to Microsoft. It is your responsibility as a Data Controller to stay compliant under the GDPR, and set up user consent collection for downstream forwarding. The consent default setting can be deprecated in the future.
Setting Name | Data Type | Default Value | Platform | Description |
---|---|---|---|---|
Tag ID | string |
Web | The ID associated with the Universal Event Tracking (UET) tag. | |
Consent Data Mapping | mapping |
null | Web | A mapping of mParticle consents to Bing Ads consents. |
Ad Storage Default Consent Value | string |
Unspecified |
Web | The default consent value to forward for the Ad Storage Field |
Was this page helpful?