BigQuery Export Data in Adobe Target for Audience Segmentation

​@Gokul_Agiwal  Can I create an additional Customer Attributes data source and upload another dataset from BigQuery?
Yes, you can do that

Can I use the same alias ID / customer ID namespace as the existing integration?
Alias id should be unique so no https://experienceleague.adobe.com/en/docs/core-services/interface/services/customer-attributes/t-crs-usecase#:~:text=Represents%20a%20source,the%20Mobile%20SDK.)

What I would recommend here is to export your BigQuery data directly in GCP and then use Adobe RTCDP flow services API to ingest data from GCP to AEP and then use those attributes from the dataset.

However please make sure

1. the data lands in a profile-enabled schema/dataset
2. the relevant identity is configured so the profile can be stitched to the web/app visitor
3. you activate the audience to the Adobe Target destination
4. during activation, you map the profile attributes you want Target to receive

Then  you can use them like this ${aep.profile.favoriteColor}

I recently implemented a personal project on this exact use case; let me know if you require the repo link

Thank you! 

Sarthak Bhatt | Senior Product Consultant | Customer Experience | Adobe  

Hi ​@Gokul_Agiwal ,

Clarification on the Alias ID / Customer ID Namespace

There is often confusion around the term "Alias ID" in Adobe Customer Attributes documentation:

• The Alias ID (Attribute Column Name) MUST be unique per Data Source: You cannot have two different Customer Attribute Data Sources both trying to set a column named CRMID or VisitorID as the primary key if they map differently.

• The Identity / Namespace Value CAN be identical: You CAN pass the exact same underlying ID value (e.g., CRMID_12345) to map data from Source A and Source B to the exact same physical visitor profile in Adobe Target.

Option 1: Dual Customer Attributes Data Sources (Standalone Target)

Since AEP is not in place, using a second Customer Attributes Data Source mapped to the same customer ID namespace is fully supported, provided you structure the schema correctly.

Key Implementation Rules:

1. Primary Key Alignment: Use the exact same Customer ID namespace (e.g., CRMID) during the setup wizard for Data Source B, and ensure target.setCustomerId or mbox3rdPartyId passes that exact ID value from the site.

2. Distinct Attribute Naming: Ensure attribute names across Data Source A (CRM) and Data Source B (BigQuery) do not conflict.

   • CRM Source: crm_loyalty_tier, crm_lifetime_value

   • BigQuery Source: bq_propensity_score, bq_churn_risk

3. Capacity Constraints: Target enforces a hard limit of 100 total Customer Attributes per profile across all active data sources combined.

4. Ingestion Latency: Updates via the Experience Cloud FTP/SFTP ingestion for Customer Attributes take up to 12–24 hours to propagate across all global Target edge clusters. This path is strictly for batch/offline segmentation, not real-time intra-session updates.

Option 2: Target Profile Update API (Direct BigQuery Pipeline)

If you need lower latency (minutes instead of 12–24 hours) without AEP, you can bypass the Customer Attributes UI entirely by using the Adobe Target Single Profile Update API.

Architectural Pattern:

1. BigQuery ETL: Export your model results/attributes from BigQuery via a Google Cloud Function or Cloud Run job.

2. Target Profile Update API: Send an HTTP POST request directly to Target's profile endpoint using the thirdPartyId (your CRM ID):

HTTP

POST https://<your-client-code>.tt.omtrdc.net/m2/<your-client-code>/profile/update?profile.thirdPartyId=CRMID_12345
Content-Type: application/x-www-form-urlencoded

profile.bq_churn_score=high&profile.bq_propensity=0.85

Why this is better for Standalone Target:

• Speed: Profiles update at the Target edge in near-real-time (usually under 5 minutes).

• Direct Targeting: The attributes land directly as profile.bq_churn_score inside Target, making them immediately available in the Target Audience Builder under Profile Attributes.