This use case looks at how to create a classification data steam with VLOOKUP.
Using a parent-child relationship isn’t always possible. Sometimes the data streams don’t have the same Entity Key mapped, which is a prerequisite for establishing a parent-child relationship. Another way to implement classifications is by using the VLOOKUP function. To update the PO Custom Attribute field, map the PO Number (Campaign Custom Attribute) within the Facebook Ads data stream using this Vlookup formula:
VLOOKUP(csv['Campaign Key'],[Campaign_Name],[PO],true,true,{'Classification Data Stream'})
If both options are viable, using the parent-child method is more efficient and scalable than using the Vlookup option. This is because the Vlookup option requires a dedicated Vlookup formula in the mapping of each attribute you wish to update. Parent-child is a single configuration that automatically updates all the attributes pertaining to a matched Entity Key. Additionally, applying classifications to new data sources requires Vlookup mapping formulas in each source, making Vlookup the less favorable option in cases where your classifications apply to multiple data sources. Also, the Vlookup command is only initiated for data that was active during the data stream’s processing period. For example, if the classification data stream is updated with a new PO value for a certain Facebook campaign, and the Facebook data stream is reprocessed for the last 10 days, the new PO value isn’t updated in the Facebook data stream if this particular campaign wasn’t active within these last 10 days. Using Vlookup is more time consuming and has a higher likelihood that certain data isn’t updated.