Pixel-based Data Transfers - Qualification | Community
Skip to main content
S
suhasRakam
Level 2
May 18, 2020
Solved

Pixel-based Data Transfers - Qualification

  • May 18, 2020
  • 5 replies
  • 5143 views

Hi All,

 

Can anyone help us how to qualify for segments which are using rule based behavior created traits. We might have bigger combination within segment, so we don't want to  navigate to all the pages and qualify.We have used demdex pixel URL's to run it in the browser in a new tab to qualify for segments, but at this point we are seeing it is not loading for us. 

example pixel URL: (http://something.demdex.net/event?d_sid=12345).

 

1) Does this way of qualifying into a segment still works? or can you recommend any other way for force qualifying segments?

2) What is the lag time for real-time qualification into a simple segment, I see there is a lag once we meet the qualification criteria but it is not consistent all the time?

 

Appreciate your time and help!

 

Thank in advance.

 

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 snielson

Hi @suhasrakam,

 

Yes, using the DCS API to send a call to AAM with the d_sid=<trait ID> will still realize the device making the call into said trait. If your segments are configured with a profile merge rule that contains device options, and contains the traits in the segment rule, it should only take a second or so to get both trait and segment qualified on the device.

 

Regards,

Shane

5 replies

snielson
Adobe Employee
snielsonAdobe EmployeeAccepted solution
Adobe Employee
May 21, 2020

Hi @suhasrakam,

 

Yes, using the DCS API to send a call to AAM with the d_sid=<trait ID> will still realize the device making the call into said trait. If your segments are configured with a profile merge rule that contains device options, and contains the traits in the segment rule, it should only take a second or so to get both trait and segment qualified on the device.

 

Regards,

Shane

S
shilpanic1
August 25, 2020

We're seeing the same issue as #2, appears to be a lag of up to several minutes.  

S
Adobe Employee
shweta_singhAdobe Employee
Adobe Employee
August 28, 2020

Hi @shilpanic1 ,

 

Real time segment qualification works in real time.There is no lag  in the segment qualification.To validate the same,you can use d_cts flag.

 

It can be used to validate the trait and segment qualification specific to a user.
 
 
 
We can further modify the above call and add additional parameter like  d_cid,d_mid,d_uuid to pull the segment and trait qualification details.
For information on usage of d_cts, you can refer to below link from our documentation.
 
Regards,
Shweta
S
shilpanic1
August 28, 2020
Thanks, @shweta_singh . We're mapping segments to a cookie destination. Is it possible the lag I'm seeing occurs after forcing the segment but before it gets written to the cookie we've specified?
ankitbhatt
Adobe Employee
ankitbhattAdobe Employee
Adobe Employee
August 28, 2020

Hi @suhasrakam ,

 

+1 to the Shweta's response.

Also, I would suggest to get it checked with the Audience Manager Support Team whether d_cts flag is enabled for your AAM Organization or not. Otherwise using d_cts=2 flag in DCS API will not return Traits & Segments to you.

 

Best,

Ankit Bhatt

S
Adobe Employee
shweta_singhAdobe Employee
Adobe Employee
August 31, 2020

Hi @shilpanic1 ,

 

Yes,it is very much possible that the lag which you are seeing could be the time,when the segment qualification is written to mapped cookie destination.

 

Regards,

Shweta

Terms & ConditionsAccessibility statement

Loading footer...