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
BedrockMission!

Learn More

View all

Sign in to view all badges

Can we include escape characters in the AT param value ?

Avatar

Avatar
Give Back 5
Level 4
LordOfTheRings
Level 4

Likes

62 likes

Total Posts

126 posts

Correct Reply

22 solutions
Top badges earned
Give Back 5
Validate 10
Validate 1
Contributor
Shape 1
View profile

Avatar
Give Back 5
Level 4
LordOfTheRings
Level 4

Likes

62 likes

Total Posts

126 posts

Correct Reply

22 solutions
Top badges earned
Give Back 5
Validate 10
Validate 1
Contributor
Shape 1
View profile
LordOfTheRings
Level 4

26-05-2021

Hi Team,

 

We are using customer attribute to upload the offline data in experience cloud.The data file contains the CustomerId as first column and we are passing this customerid in the thirdPartyId in the target call.

The customerId value in data file is in doublquotes however the value that we are passing in thirdPartyId is without doubl quotes so targeting doesnt work using crs data source.

As a workaround we used escape characters in the code at target end so that value in double quotes is passed

Now I can see the value passing like this and the targeting also works:

LordOfTheRings_0-1622026912539.png

 

 

so wanted to ask if this fine and it would not break anything else.

 

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Give Back 25
Employee
ryanr701
Employee

Likes

197 likes

Total Posts

207 posts

Correct Reply

84 solutions
Top badges earned
Give Back 25
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Give Back 25
Employee
ryanr701
Employee

Likes

197 likes

Total Posts

207 posts

Correct Reply

84 solutions
Top badges earned
Give Back 25
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
ryanr701
Employee

26-05-2021

Hey @LordOfTheRings,

I'm sure you already know the top recommendation: Fix the customer attributes data file so it doesn't have the double quotes surrounding the ids.

In help for ECID and Customer IDs the docs do say to NOT use encoded values in your ids (within the "important" section). Which I guess you are still okay on since your just escaping the quotes. If you are not using the visitor.setCustomerIds() method, but the alternative method of directly passing the customer ID to Target as the thirdPartyId I don't see any documentation on special character limits.

I can't think of it causing other issues if it is working for you; however, I think the much better solution is to fix the source.

Hope that helps!