3796425 - CDC Profiles Contain Unexpected data.* Field Values (Wrong Brand, Application Code, or Locale) After Registration via Third-Party Integration

After a consumer registers on a site, the resulting CDC profile contains custom data.* field values that belong to a different brand, product, or country context. Typical observations include one or more of the following:

• data.initialAppSourceCode is set to a value from a different brand or campaign (e.g., CLCHOCOLATE_WHATSAPP) instead of the value expected for the registering site
• data.externalApplication.applicationCode references a different product or app
• Subscription/preference objects carry tags arrays with a wrong sourceApplication: value
• profile.locale reflects the wrong country (e.g., es-mx instead of es-cl)
• Phone numbers carry the wrong country dialling code

The issue is consistent — every new registration from that site produces the same incorrect values — rather than sporadic.

• Platform: SAP Customer Data Cloud (Gigya CDC)
• Product Area: Account Registration, Data Schema, accounts.setAccountInfo / accounts.register
• Integration Layer: Drupal CMS (or any third-party system calling CDC APIs directly)
• Affects: Any CDC site where the registration payload is assembled by an external system rather than by the CDC Web SDK or RaaS screen-sets

InitialAppSourceCode, wrong source code, incorrect source code, data field incorrect value, custom data field, data schema, template cloned, copied template, Drupal integration, externalApplication, applicationCode, sourceApplication tag, profile locale wrong, locale es-mx es-cl, wrong country code, phone country code, wrong brand, CLCHOCOLATE_WHATSAPP, TRENCITO, recetasnestle, registration payload, accounts.setAccountInfo, accounts.register, RaaS, third-party integration, data mapping, data field not expected, profile data incorrect, bulk remediation, backfill, CDC data schema, site cloned, integration misconfiguration , KBA , CEC-PRO-RAS , RaaS (Screen-Sets, Site Policies, Schema) , Problem