...
If we are fetching publishers' users' traffic, the collection can be done through WamFactory logs tags, as seen in the diagram above.
For WAM clients using a Wamfactory tag, javascript that they can implement in their website, user traffic can be collected through Wamfactory logs.
Server-side Integration
For clients not using WAM or for those using WAM but not a Wamfactory tag, collection can be done through a server-side integration (files pushed to S3/GCS bucket or even through a Snowflake share if the Publisher is using Snowflake.)
Activation
For activation, the process differs depending on whether it’s being done through open real-time bidding or direct deals.
Direct Deals
If the publisher has a campaign for a brand that they have a direct deal with, they can use an ad server to launch the campaign for that advertiser. They currently have two possibilities for activation, they can either use Xandr or Google Ad Manager. If they use Xandr, we can provide delivery for users on the server side, so we can push user profiles directly to Xandr and they can handle the activation on their side. If they are using the Wamfactory wildcard JS, activation to GAM can be done via the Wamfactory tag. When sending files in server-side mode, the client should provide the schema to the Product so that the Data Enrichment team can use the proper decoder to process the files.
All files must include:
An ID
URL
Geolocation (normally an IP address)
Files must be compressed and normally are in JSON format but CSV is also acceptable.
On the Product side, a dedicated touchpoint (or set of touchpoints) will be created to isolate this data on Data Enrichment side and a dedicated Owner will be set up to link the touchpoint(s) to the Behavioral Client Account.
Activation Targets
Publisher Target(s) for activation purposes can be a mix of the following Target types :
WAM
DSP Platform : Xandr; DV360
“bucket delivery “ : Amazon S3; GCS…
DataHub (SnowFlake )
🛑Prebid🛑
Product Evolution is needed here!
...