During the MoonFish setup process for publishers, there are two points we need to take into consideration; how we will collect and to where and in which way we will activate.

Collect

When setting up MoonFish for a new publisher client, we need to check first how we can collect their traffic. We can either fetch publishers' user traffic or retrieve it via a server-side collection.

Fetching Publisher URLs

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.

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.

🛑Prebid🛑

Product Evolution is needed here!

If we want to offer the possibility to collect and activate Publisher traffic based on the Weborama Prebid. js module, we’ll need to improve it to be able to collect and handle two new ids types:

• Universal IDs (FirstId ; Utik Id; ID5…) to collect non-logged user traffic

• Crm Ids (emails; client ids…) to collect logged user traffic