Can we have multiple declared ids with same integration code | Community
Skip to main content
keerthivasanj96
keerthivasanj96
Level 3
April 15, 2020
Solved

Can we have multiple declared ids with same integration code

  • April 15, 2020
  • 1 reply
  • 10632 views

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_id30005253601 - CRM ID
d_cid_ic: customer_id63546356363 - KAKAO ID
ts: 1586966266141

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

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

1 reply

snielson
Adobe Employee
snielsonAdobe EmployeeAccepted solution
Adobe Employee
April 15, 2020

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

    snielson
    Adobe Employee
    snielsonAdobe Employee
    Adobe Employee
    May 8, 2020
    @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".
    Terms & ConditionsAccessibility statement

    Loading footer...