Rolling window data backup within Domo

History

Promoting is switching rapidly, and so is the facts that arrives with it. Our company brings together data from companies these kinds of as Facebook Ads, Google’s Campaign Supervisor 360, Google Ads, Bing Adverts, Snapchat, and other folks so we can monitor and enhance advertising campaigns throughout channels alongside one another in Domo. 

Nonetheless, some of the products and services mentioned above delete data from their procedure just after 24 months. Additionally, simply because advertising knowledge can alter up to 90 times (or extended!) after an action has transpired (as attribution modeling updates or fraudulent clicks are removed), we are intrigued in a rolling window of info.

When pulling details, we can simply change date ranges in pre-built Domo connectors and use the append operation to capture historical knowledge. We can then produce a protected haven within just Domo for our data and know that it will not get deleted. 

Nonetheless, even though Domo has 99% of the connectors we need to have, occasionally we have to have to operate with the Domo API to create a custom made answer.

Challenge statement

Let’s say I’ve formulated a alternative that pulls details from 91 days in the past until finally yesterday into Domo. I want to help save the historic information just after that 90-working day rolling window (the 91st day) but I do not want to shell out time redeploying my answer with a diverse day variety in the pull. 

Alternative assertion

We can leverage the DataSet Duplicate Unload Connector to make a loop in just Domo that backs up facts. This connector is effortless to use. All you have to do is established up Domo API credentials, then specify the Dataset ID you want to duplicate and the Domo instance you are grabbing the knowledge from. 

Demo

First, we set up an ETL that employs a filter-formulation to get the information and facts from 91 days ago from our personalized relationship. Then, we use the DataSet Duplicate Unload Connector with the dataset ID from the dataset developed by the ETL, set the update method to append, and established it to run on a program to update in advance of the primary relationship runs yet again. 

Just like that, you have received your historic details from a rolling window of info risk-free in Domo. I hope this write-up was handy and released you to one thing new in Domo.