not sending network call to Target on every page & datastream overrides & sharing audiences between cdp and Target using at.js

[Michael_Soprano]

Customer would like to implement CDP with Target using WEB SDK. However its www has lots of page views. Then he would like to not turn on Target on every page but only on some (to not generate Target network calls -> cut costs). I come up with the solution that on some pages we can use Datastream Overrides. It would be two datastream:
1. First - Target turn on
2. Second - Target - turned off

The other solution is to implement Target using at.js and then turning it on only on particular urls. But then are we able to share audiences between Target and CDP?

[bjoern__koth]

Are you using Web SDK Guided Events to separate Target from Analytics calls?

That would potentially be the easiest, having separate rules where one takes care of Analytic page views and the other of Target.
Latter could be easily configured to not fire too often.

https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/applications-setup/setup... > "Splitting Personalization and Analytics requests"

[Michael_Soprano]

I did not consider Analytics in that implementation. 

If you turn on Target in Datastream is it possible to not send page view event in Tags -> Rules? On the other hand we would like to send that page view still to CDP. 

Just looking at the rules I do not see that option

Greeting from Warsaw!

[Parvesh_Parmar]

Hello @Michael_Soprano ,

If I understand correctly, the definition of a data stream override means that during the action configuration, you can send data to a different data stream instead of the default one. In other words, while one data stream is set as default, you can direct the data to an additional data stream based on specific conditions.

For reference:https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/web-sdk/web-sd...

Now, let me break it down further with an example:

1. Creating Two Data Streams

Let's say you create two data streams:

• One for Target as a service
• One for AEP as a service

At this point, you have two services available within your configuration.

2. Setting the Default Data Stream

In the extension configuration, you need to choose one of these two data streams as the default. For this example, let's assume you select the AEP data stream as the default.

3. Setting Up rules

Next, you need to configure two event rules:

1. First rule (Default Data Stream)
   This event will trigger on every page view without any specific condition. It will always send data to the AEP dataset (your default data stream) for each page load.

2. Second rule (Conditional Data Stream Override)
   Here, you can set up a rule with a specific condition. For example, if a page view occurs and the URL matches a particular page (say Page B), this rule will trigger an action.

   In this case, you want to send data to Target only for Page B. In the action, you will use the data stream override to specify the Target data stream. This ensures that the data for Page B is sent to the Target service, instead of the default AEP data stream.

Example:

• If a customer visits Page A, Page B, and Page C:
  • The first rule will trigger for all pages, sending data to AEP for every page load.
  • The second rule will only trigger when Page B is loaded, and it will send the data to Target using the data stream override.

I hope this helps clarify the concept of using data stream overrides!

Best regards,
Parvesh

[Michael_Soprano]

Thanks for such an extensive reply.

But when I send data to Target I still want to send page view event to AEP. So in this case:

• One for Target as a service - I need to add both Target and AEP to fulfill my scenario?
• One for AEP as a service - This stays the same

I want to send events on every page view to AEP but on only some to Target (and still send to AEP). Its because I want to limit network calls to Target to cut costs 

[dwright · Accepted solution]

@Michael_Soprano ,

I would pause for a moment and reach out to your Adobe account team (or your client's if you are a consultant). The Target contracts are usually designed so customers don't have to worry about things like this. I would check with the account team to confirm if they need to be concerned about this before moving into a less standard implementation. (And if you have and they do, my apologies! )

[SSampsa]

Absolutely so, the override is to change the configuration ID used, just as you said. This solution would be my suggestion as well and we have done this, but for different reasons (swap data stream based on consent and security control to limit loading of external content for some pages).

There are some effects of course, as Target is assumed to be running on each page as @dwright stated, but there are valid cases to do so.