not sending network call to Target on every page & datastream overrides & sharing audiences between cdp and Target using at.js | Community
Skip to main content
Michael_Soprano
Level 10
October 11, 2024
Solved

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

  • October 11, 2024
  • 1 reply
  • 1426 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by dwright-adobe

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 


@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! 😄 )

1 reply

bjoern__koth
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
October 11, 2024

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-target > "Splitting Personalization and Analytics requests"

Cheers from Switzerland!
Michael_Soprano
Level 10
October 11, 2024

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!

dwright-adobeAdobe EmployeeAccepted solution
Adobe Employee
October 14, 2024

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 


@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! 😄 )