Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Retroactively importing data into an eVar after it has been set

andylunsford1
Level 2
Level 2

Hello!

 

I have a unique use-case that I've been trying to solve.  We have a public facing website, where we capture an identifier for a user through an email that contains the user ID in the link.  When a user comes to the site through the link, we can capture all future data as being tied to the user through the eVar, but we are unable to tie it to the user in the past if the date range doesn't include when it was set for the user.

 

Is there a way to insert data into an eVar that was previously unspecified in the past that has now been identified?  I've looked at the Data Repair API, and it seems like when it's out of beta could assist here, but I wanted to confirm I wasn't overlooking a simpler approach in the interim.

 

Thanks!

Data Import evars
1 Accepted Solution
ishans52004352
Correct answer by
Employee
Employee

Data Sources has a specific template/format via which the data is uploaded. But if you try uploading again via Full Processing Data Sources, we might see double metric/instances. If the objective is to delete existing data and then re-upload the correct data, our Engineering Services team is the option here (via your CSM), or we can wait for the feature to be available in Data Repair API.

View solution in original post

4 Replies
ishans52004352
Employee
Employee

Hi @andylunsford1 ,

You can use Full Processing Data Sources to import data into historical date ranges.

https://docs.adobe.com/content/help/en/analytics/import/data-sources/datasrc-home.html

Data Repair API is to correct the historical data which might not be a suitable use case here (moreover the ability to repair data for evar isn't rolled out yet).

Thanks!

andylunsford1
Level 2
Level 2
@ishans52004352 To confirm I'm understanding the correct approach with Data Sources, would I just export the data from Data Warehouse and import again with the value for v25 being specified? I want to make sure I'm not duplicating the hit data when I import v25.
ishans52004352
Correct answer by
Employee
Employee

Data Sources has a specific template/format via which the data is uploaded. But if you try uploading again via Full Processing Data Sources, we might see double metric/instances. If the objective is to delete existing data and then re-upload the correct data, our Engineering Services team is the option here (via your CSM), or we can wait for the feature to be available in Data Repair API.

View solution in original post

andylunsford1
Level 2
Level 2
Thanks for confirming, it seems like the latter is the better option for us, as this will be an ongoing identification adding previously unknown data rather than deleting and needing to reupload data. Thanks again for confirming!