A Business Owner

Unique Delighting Business

Rolling window data backup within Domo

Rolling window data backup within Domo

Track record

Advertising is shifting speedy, and so is the details that arrives with it. Our company combines information from providers these as Facebook Advertisements, Google’s Campaign Supervisor 360, Google Adverts, Bing Adverts, Snapchat, and other people so we can keep track of and enhance advertising campaigns throughout channels alongside one another in Domo. 

Nonetheless, some of the providers shown previously mentioned delete data from their process following 24 months. Additionally, due to the fact marketing data can change up to 90 times (or for a longer period!) immediately after an motion has transpired (as attribution modeling updates or fraudulent clicks are eliminated), we are intrigued in a rolling window of info.

When pulling details, we can quickly change date ranges in pre-crafted Domo connectors and use the append operation to seize historical facts. We can then develop a safe and sound haven inside Domo for our knowledge and know that it won’t get deleted. 

Nonetheless, whilst Domo has 99% of the connectors we will need, in some cases we have to have to work with the Domo API to create a custom made answer.

Trouble assertion

Let us say I have created a resolution that pulls data from 91 days ago until eventually yesterday into Domo. I want to help you save the historic information following that 90-day rolling window (the 91st working day) but I do not want to devote time redeploying my solution with a distinctive day vary in the pull. 

Option statement

We can leverage the DataSet Duplicate Unload Connector to build a loop inside of Domo that backs up facts. This connector is uncomplicated to use. All you have to do is set up Domo API credentials, then specify the Dataset ID you want to copy and the Domo instance you are grabbing the data from. 


First, we established up an ETL that takes advantage of a filter-system to get the details from 91 times back from our customized relationship. Then, we use the DataSet Copy Unload Connector with the dataset ID from the dataset produced by the ETL, established the update method to append, and set it to run on a program to update just before the original relationship runs yet again. 

Just like that, you have got your historical facts from a rolling window of details safe and sound in Domo. I hope this article was valuable and introduced you to some thing new in Domo.