Open

During the GoldenFish 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 GoldenFish for a new publisher client, we need to check first how we can collect URLs. We can either fetch publishers' URLs or retrieve URL content via a RSS feed.

Fetching Publisher URLs

If we are fetching publishers' URLs, collect can be done either through WamFactory logs or GoldenFish tags, as seen in the diagram above.

For clients not using WAM or for those using WAM but not a Wamfactory tag, collect can be done through a GoldenFish tag. The publisher can implement the contextual tag:

<script async src="https://cstatic.weborama.com/bigsea/contextual/v1/weboctx.min.js"></script>
    <script>
      window.weboCtx = window.weboCtx || [];
      // COLLECT ID
      weboCtx.push(function() {
        this.collectURL({
          debug: false
          clientID: <GoldenFishClientID>, // mandatory. 
          targetURL: document.URL
        });
      });

You can learn more about this process here.

For WAM clients using a Wamfactory tag, javascript that they can implement in their website, URLs can be collected through Wamfactory logs.

RSS Feed

In some cases while a client might have public content, it may not be possible for us to fetch all of the content if they have a paywall (requiring users to subscribe to read their full articles). If they have a RSS feed they would be able to provide this to us to be able to pull the URL content from there. If we aren’t able to fetch URLs or the client doesn’t have a RSS feed, then the client can push the URL, title and content in json files to an AWS S3 bucket so we can ingest the content.

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 adserver to launch the campaign for that advertiser. They currently have two possibilities for activation, they can either use Smart Ad Server or Google Ad Manager. If they use Smart Ad Server, we can provide delivery for URLs on the server side, so we can push URL profiles directly to Smart Ad Server and they can handle the activation on their side. If they use GAM and can use Prebid, they can either use the Weborama Realtime Segment Module to set targeting to GAM (which is preferred), or if they are using the Wamfactory wildcard JS, activation to GAM can be done via the Wamfactory tag. If they are not using the Wamfactory wildcard JS, we can set the GAM targeting via the GoldenFish tag. You can learn more about activation to GAM here.

Prebid

The publisher can use the Weborama RTD module to activate to GAM, we will need to create an API token for them. Publishers can add the below configuration to their Prebid config:

pbjs.setConfig(

    ...

    realTimeData: {

        auctionDelay: 5000, // optional

        dataProviders: [

            {

                name: "weborama",

                waitForIt: true,

                params: {

                  weboCtxConf: {

                      setTargeting: true,

                      token: "<<token provided by weborama>>",

                      targetURL: "..." // default is document.URL

                    }

                }

            }

        ]

    }

    ...

}

You can find more information about this here.

Open RTB

For publishers who want to sell their inventory programmatically through open RTB, they might use prebid.js which will allow them to do this. In this case, they can use the Weborama Realtime Segment Module to propagate contextual segments to bidders (which we prefer). However if they are not using prebid.js, we can push the contextual segments to their SSP on the server side if we have a bridge with them.