Hi Adobe Community,
Case
Our team is working with a client who requested to store vouchers data into RTCDP as a profile attribute to keep record of what vouchers each individual profile holds. Data wished to be included are: email, voucher expire in 7 days, owned coupons and used coupons. The ultimate goal is to create audience for voucher expiration activation.
Example
On Day 1, a profile owns 3 coupons, 2 of which will expired in 7 days and used 1 coupon. On Day 2, the profile purchased 2 additional coupon and have used 1 additional coupon, which makes the profile to own 4 coupons and have used 2 coupons.
Day 1
couponExpiredIn7Days | ownedCoupons | usedCoupons | |
xxx@example.com | xxx123, xxx234 | xxx123, xxx234, xxx456 | xxx345 |
Day 2
couponExpiredIn7Days | ownedCoupons | usedCoupons | |
xxx@example.com | xxx234 | xxx234, xxx456, xxx567, xxx678 | xxx123, xxx345 |
The Question
In case client could only send us the daily updates on the change status of the coupons, is there a way we can insert the additional records and remove obsoleted records without needing to receive the full data of all past record? i.e. record from client will only show which are the newly added coupons and 1 coupon was used. Alternatively, should we ask client for a full record for all coupons to ingest update and replace these attributes on a daily basis?
Kindly share your thoughts on the proper handling of this matter.
Thanks a lot!
Zac
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hello @ZacharyTa1
What are the activation requirements for this use case? Are there specific data elements which need to part of the audience to activate the audience to the destination platforms?
As you have indicated when data is written to a profile level attribute you need to write the entire dataSet since this is record based. If you wish to track items over time you can use the time series experience event schema.
Other items to consider is the email address to a coupon 1:1 or can other email address redeem the same coupon/voucher?
I would review the following article in regards to coupon level data.
Hello @ZacharyTa1
What are the activation requirements for this use case? Are there specific data elements which need to part of the audience to activate the audience to the destination platforms?
As you have indicated when data is written to a profile level attribute you need to write the entire dataSet since this is record based. If you wish to track items over time you can use the time series experience event schema.
Other items to consider is the email address to a coupon 1:1 or can other email address redeem the same coupon/voucher?
I would review the following article in regards to coupon level data.
Views
Likes
Replies