What advertising audiences are available in Ignite

1. Ad networks (Google, Facebook, Instagram, Trade Desk/Display, Etc) maintain identity records on all the visitors they see on their networks.

2. In order to target visitors on these networks you need to provide them with an identifier that they can match to these visitors.

3. This identifier usually is in 1 of 2 flavors:

   1. Derived from their email address or phone number

   2. A cookie ID that is saved within their web browser that can be synchronized with the identifiers on the ad networks. This is dependent on Third Party Cookies and will have varying effectiveness depending on web browser privacy policies.

4. Basically, you give the network a list of identifiers for people that you want to target, they match them to known people on their network and surface them to you as an Audience that you can traffic ads to.

If an ad network pixel from Facebook/Meta or Google is present on a website that also has the Ignite pixel installed, we can push those visitors into Google & Facebook accounts for that pixel, along with their segments.

Again, this will only work if web browsers allow third party cookies.

Ignite can leverage its identity resolution to build lists of visitors from their hashed email and phone identifiers that are not dependent on third party cookies. This list may overlap with the Cookie audiences above, but will also have some visitors in it that are unique.

You should use both. If your retargeting pixel is in place, you can capture segmented audiences with that and you can also upload advertiser IDs, available in our API or via Audience Export, to use in campaigns. Meta and Google will deduplicate any overlap and you will get maximum reach for our audiences for your campaigns.