Rolling window knowledge backup inside Domo

0
129
Rolling window knowledge backup inside Domo


Background

Promoting is altering quick, and so is the information that comes with it. Our company combines knowledge from providers equivalent to Fb Adverts, Google’s Marketing campaign Supervisor 360, Google Adverts, Bing Adverts, Snapchat, and others so we will monitor and optimize promoting campaigns throughout channels collectively in Domo. 

Nonetheless, a number of the providers listed above delete knowledge from their system after 24 months. Moreover, as a result of promoting knowledge can change as much as 90 days (or longer!) after an motion has occurred (as attribution modeling updates or fraudulent clicks are eliminated), we’re focused on a rolling window of information.

When pulling knowledge, we will simply change date ranges in pre-built Domo connectors and use the append performance to seize historic knowledge. We will then create a secure haven inside Domo for our knowledge and know that it received’t get deleted. 

Nonetheless, whereas Domo has 99% of the connectors we want, typically we have to work with the Domo API to create a customized resolution.

Drawback assertion

Let’s say I’ve developed an answer that pulls knowledge from 91 days in the past till yesterday into Domo. I need to save the historic knowledge after that 90-day rolling window (the 91st day) however I don’t need to spend time redeploying my resolution with a distinct date vary within the pull. 

Answer assertion

We will leverage the DataSet Copy Unload Connector to create a loop inside Domo that backs up knowledge. This connector is simple to make use of. All it’s a must to do is ready up Domo API credentials, then specify the Dataset ID you need to copy and the Domo occasion you’re grabbing the information from. 

Demo

First, we arrange an ETL that makes use of a filter-formula to seize the knowledge from 91 days in the past from our customized connection. Then, we use the DataSet Copy Unload Connector with the dataset ID from the dataset produced by the ETL, set the replace mode to append, and set it to run on a schedule to replace earlier than the unique connection runs once more. 

Similar to that, you’ve obtained your historic knowledge from a rolling window of information secure in Domo. I hope this publish was useful and launched you to one thing new in Domo.






Supply hyperlink

LEAVE A REPLY

Please enter your comment!
Please enter your name here