Integrations
Yahoo (formerly Verizon Media) is a global media and tech company that connects people to their passions. Yahoo provides a full-stack platform for businesses to amplify growth and drive meaningful connections across advertising, search, and media.
The Yahoo DSP gives its customers programmatic access to Native Marketplace inventory, formats, targeting and measurement together in a single platform. The DSP gives advertisers a unified solution to control every aspect of their buys - from planning, buying and management, to insights and optimization - across all formats and exclusive inventory opportunities.
In order to forward an mParticle audience to Yahoo you will need to work with your Yahoo Account Manager to get your Master Data Management (MDM) ID that corresponds to your organization. Please note that the MDM ID cannot be changed after the configuration has been created.
The Folder Name provided during configuration of the Integration is used as the name of the Parent Folder under which all audiences created within Yahoo will be located. To be accepted by Yahoo, the Folder Name must be less than 255 characters in length. Please note that the Folder Name cannot be changed after the configuration has been created.
Note that while the newly created folder should typically be available in Yahoo within minutes of setting up the initial Integration configuration, this process can take a longer time depending on the Yahoo system load. Please allow up to four hours for your folder to appear on your Yahoo dashboard.
When forwarding audiences to Yahoo, mParticle sets the name based on the External Audience Name.
Depending on the Connection Settings, mParticle will forward one or more of the following IDs to match users:
mParticle uses the GDPR Protected User Attribute to group users, informing Yahoo of which users are EU residents and which are not.
When this setting is not enabled, or when the value is absent for a user, or when the value cannot be parsed as boolean, or when the value parses as true
, Yahoo will apply GDPR restrictions to the user.
When the setting is enabled, and the value is present for the user, and the value parses as false
, the user is recognized as a non-EU resident and is exempt from GDPR regulations.
Note that this setting is not associated with or dependent on any consent features or functionality native to mParticle. Before enabling this setting, it is recommended that you refer to Yahoo documentation to verify that the described behavior is still valid.
User identity data sent to Yahoo expires after a period of 45 days.
The Yahoo Integration uses Bulk Forwarding. Bulk Forwarding means that, instead of uploading updates to an audience in real time, mParticle compiles updates into a queue until either a given amount of time has passed since the last upload, or until a certain batch size has been reached.
By default, mParticle uploads to Yahoo whenever at least one of the following conditions is met:
Upload frequency can sometimes be adjusted. Reach out to your mParticle Customer Success Manager if you need to discuss upload frequency.
mParticle doesn’t delete the downstream audience when you delete an audience from mParticle.
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Master Data Management ID | int |
The Master Data Management (MDM) ID obtained from your Yahoo account. Note that the MDM ID cannot be modified without recreating the configuration. | |
Folder Name | string |
The name of the folder under which your Audience data will appear on your Yahoo dashboard. Note that Folder Name cannot be modified without recreating the configuration. |
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Forward Emails | bool |
true |
If enabled, and the user’s e-mail address is available, the SHA-256 hash of that e-mail address will be added to the audience |
Forward IDFAs | bool |
true |
If enabled, and the user’s IDFA is available, it will be added to the audience |
Forward GAIDs | bool |
true |
If enabled, and the user’s Google Advertising ID is available, it will be added to the audience |
GDPR Protected User Attribute | string |
Specify the key of the user attribute that determines if a user is subject to protection under the GDPR. The value will be parsed as a Boolean to allow Yahoo to apply GDPR restrictions on a per-user basis. |
Was this page helpful?