Can we have multiple declared ids with same integrati...

[keerthivasanj96]

We are planning to integrate kakao and AAM for one of our use case , where we need to onboard kakao id along with our company crm id in dcs call. We are unsure it is good to have both ids with same integration code in dcs calls, also we need to know how that behaves. Could you please help us on this.

Example

d_visid_ver: 2.4.0
d_fieldgroup: AAM
d_rtbd: json
d_ver: 2
d_mid: 55049628266143632253362635576663235169
d_blob: RKhpRz8krg2tLO6pguXWp5olkAcUniQYPHaMWWgdJ3xzPWQmdj0y
d_cid_ic: customer_id
3000525360
1 - CRM ID
d_cid_ic: customer_id
63546356363 - KAKAO ID
ts: 1586966266141

[snielson · Accepted solution]

Hello,

Both Ids will be stored under the same data source, and linked to the same AAM UUID.
I may suggest setting up a new data source with a separate integration code, so you could export these IDs separately in the future, or segment them separately.

Keep in mind if you do use two separate data sources, you'll need to include them in a profile merge rule (last authentication or current authentication) if you plan on segmenting the cross-device IDs into a segment.

However, there are technically no issues if you want to store both IDs within the same data source.

Regards,

Shane

[keerthivasanj96]

Thanks for your input shane

[keerthivasanj96]

@snielson I need to check one more thing, onboading multiple ids with the same data sources will lead to increase the audience base in the segments right? Which means we could get incorect customer counts that qualified for the segment right?

[snielson]

@keerthivasanj96, yes by onboarding multiple Ids to the same data source, it could increase the segment population based on both Ids. By splitting the stored IDs into their own data source, you have more control on the type of IDs you'd want segmented based on your profile merge rules.

[keerthivasanj96]

@snielson Continuing to clarify one more doubt on this, if we pass kakao id in different datasource like this d_cid_ic: hm_id
63546356363
0 - KAKAO ID and trigger this on each load of the page with unauthstate "0", could that be stored in device profile ?. If it is stored in device profile, can we use that as alternate for UUID in export file?

[snielson]

@keerthivasanj96, the auth state 0 will kick off an ID sync so the UUID (device profile) is stored in the CRM (cross-device profile) to stitch the device and CRM together. When using auth 0 we'll also read traits from the CRM profile, much like "last auth" and will not write traits back to the profile. These IDs can be used to export out device or CRM IDs from the data source with integration code "hm_id".