Jebbit Ideas Portal
Tell us which features you would love us to build!
Tell us which features you would love us to build!
Currently, the ability to use a campaigns existing DPF mappings with other campaigns either in a same brand or in a new brand is impossible. This makes it very difficult for brands to use an experience that has DPF mappings as a template or localization as the mappings and logic will need to be redone for every campaign.
First Issue: When copying an experience with DPF in an account, you can maintain mappings. However, the DPF between the original and the copy appear to be linked, making it so any changes to the copy's feed affect the original, unless you delete the feed and start from scratch. This poses an issue because with most brands there will be changes to the feed (ex. different products), however the logic should remain the same. This makes it necessary to completely rebuild the mappings with every single copy. The example I include in my video is a simple one, however, many brands are using DPF for very complex product finders which have relatively complex mapping requirements in order to work.
Second Issue: When copying an experience over to another brand (a common use case for a localization), you can't copy over a DPF feed and the existing mappings, which adds a layer of complexity to a localization that most clients are not aware of. Similar to the first issue, this requires that customers start the mappings and uploads from scratch each time they try to localize an experience to a new brand.
Goal Solution: Ideally, we'd be able to copy over a feed and related mappings and have any copies not have the DPF connected.
Video: https://www.loom.com/share/e45936ad80a2498dbe01dfc72954583a?sid=8dc80607-10f7-4b35-9408-c2324cc62016
If I could vote for this 100x I would. I do not want to take over Emily's request, but we are also running into this with Coty too.
Emily, thanks for the Loom, very helpful. This makes a lot of sense. As you can imagine the two painpoints (intra brand and cross brand) are entirely different bodies of work, but you still make a really strong case for why this makes sense.
My thought was for the intra experience copying, we need a new option to allow the user to update an existing feed without impacting other campaigns (it would create a new feed). If the new feed has new columns (which wasn't the case in your Loom) we'd warn the user it could impact the mappings. Does this solve the intra experience painpoint?