I’m currently learning and testing how to import a CSV into Adobe RT-CDP. I’ve created a Profile Schema called test-ogd-profiles-basic.
However, I noticed something odd: the schema doesn’t include fields like first_name or last_name by default. Is that expected behavior for a profile schema?
When I tried to add a new field called first_name, the interface required me to assign it to a Field Group. This raised a question:
What is the “correct” Field Group for first_name and other similar fields from my CSV?
I initially thought the Person Identifier Field Group might work, but inside it, I don’t see any option for first_name.
Any guidance on which standard Field Groups should be used for name, contact details, and address fields would be greatly appreciated.
CSV:
person_id,email,phone,first_name,last_name,birth_date,gender,street_address,city,region,country_code,postal_code,consent_marketing,opt_in_date
CUST-0001,ana.rojas@example.com,+51-999888777,Ana,Rojas,1991-06-12,F,Av. Arequipa 1234,Lima,Lima,PE,15046,true,2024-11-01
CUST-0002,carlos.mendoza@example.com,+51-988777666,Carlos,Mendoza,1985-02-25,M,Calle Los Robles 567,Surco,Lima,PE,15039,false,
CUST-0003,mariana.perez@example.com,+51-977666555,Mariana,Pérez,1993-12-03,F,Jr. Junín 230,Miraflores,Lima,PE,15074,true,2025-01-15
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @OmarGo2
yes, that is the default blank Profile schema which requires you to either assign predefined field groups like "Personal Contact Details", Demographic Details or to create your own field groups with the exact data structure you need (e.g. using the Person Name data type) to fill your schema with life.
In general, Adobe recommends using the ootb field groups whenever possible, but sometimes these are just not enough to depict your data properly. One thing to mention is that building up your own data structure will create its own namespace, starting with an underscore like _yourcompany to avoid conflicts with other standard fields.
Reason why your out of the box schema does not automatically come with those fields are for instance that you can have different Profile schemas for different purposes and data sources, and only some may require e.g. the first name.
The Profile Service will take care of the stitching in the Union Schrma where all profile enabled schemas of your Profile class will be brought together.
Views
Replies
Total Likes
Hi @OmarGo2
yes, that is the default blank Profile schema which requires you to either assign predefined field groups like "Personal Contact Details", Demographic Details or to create your own field groups with the exact data structure you need (e.g. using the Person Name data type) to fill your schema with life.
In general, Adobe recommends using the ootb field groups whenever possible, but sometimes these are just not enough to depict your data properly. One thing to mention is that building up your own data structure will create its own namespace, starting with an underscore like _yourcompany to avoid conflicts with other standard fields.
Reason why your out of the box schema does not automatically come with those fields are for instance that you can have different Profile schemas for different purposes and data sources, and only some may require e.g. the first name.
The Profile Service will take care of the stitching in the Union Schrma where all profile enabled schemas of your Profile class will be brought together.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies