Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

URL vs. S2S Destinations

Avatar

Level 5

Good morning,

I've recently created a couple URL destinations to push segments to Google's RLSA and I was wondering if the Adobe UI is different for URL destinations when compared to a S2S destination?

Looking at a S2S destination I see:

Segment ID, Segment Name, Description, Addressable Audience, Match Rate, Status, Start Date, End Date and Mapping.

Looking at my URL destinations I only see:

Segment ID, Segment Name, Description, Status, Start Date, End Date and Mapping.

Since I only created these last week I'm wondering if the display is not showing Addressable Audiences and Match Rate because the destination is so new or if they will never show for a URL destination.

Please advise. Thank you. Glenn

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hello Glenn,

Thank you for reaching out to us!

Your understanding is absolutely correct, URL and S2S destinations are indeed unique. The mentioned metrics will be available in case of S2S destination but for URL these numbers won't show up.

View solution in original post

4 Replies

Avatar

Correct answer by
Employee Advisor

Hello Glenn,

Thank you for reaching out to us!

Your understanding is absolutely correct, URL and S2S destinations are indeed unique. The mentioned metrics will be available in case of S2S destination but for URL these numbers won't show up.

Avatar

Level 5

Thank you. Can you please let me know how I can then validate that my URL destinations are working properly?

Avatar

Employee Advisor

glennb29356951​,

You can validate by looking at the URL in the network tab within the browser.

Also, you can follow this link to see how APIs can help in validating whether the URL destination was fired for given user or not.

Avatar

Level 5

Hello,

So I learned that the destinations had not been mapped at the Google side of things. They are being mapped today. How quickly will I be able to validate the URL in the browser?

Glenn