# Schedule the Integration task runs

Now you have your MM Integration created and filled with data collected from source Integrations and transformed in accordance with the set data transformation flow.

To ensure the data's relevance, we will set an Integration tasks runs schedule for the MM Integration, too, as source Integrations are going to be updated following their Schedule rules that were set here.

As you remember, the data collection Schedule rules are created and managed on the **Schedule** page of your Integration. Same as for the other pages, when you open it for the first time, it's empty:

ℹ

Info:

Schedule rules of all the Integrations of your account are available in theSchedulesection of it.

## What is a Schedule Rule

Just like for the source Integrations, a Schedule rule is a set of parameters for an Integration task to run with. That being said, the set consists of the Integration task run parameters (1) and a scheduling tool plus an on/off switch (2), see the **Create a Schedule Rule** dialogue:

So if you need a certain Integration task to run on a certain schedule, you just create a Schedule rule for it.

## Statistics update chain

When setting the MM Integration's schedule, the best practice would be to take into consideration all of its source Integrations' Schedule rules and form a statistics update chain - a chain of data updating Integration tasks, e.g.:

Getting back to our MM Integration. Let's take a look at its source Integrations Schedules:

Looks like we have 4 Schedule rules to follow. Let's look at the following two ways of doing it:

### 1. General way

We'll create two MM Integration Schedule rules, one following the rules that update source Integrations' statistics for the last 30 days date range and the other one - for the last 7 days. Like this:

All those Schedule rules will make this statistics update cycle:

Main disadvantage of this way is that BOTH Integration's data will be re-collected. It's not bad with the given time gap between source Integrations own updates. However if those were longer, Merge Module Integration would be re-collecting the very same data that it would already have from one of the source Integrations.

### 2. Specifying the source Integration

Since we have such an Additional parameter for Integration tasks as **Inputs**, we can specify the Integration whose data we want to re-collect in each task. Let's leave one hour gap between the source Integration task run and the Merge Module Integration task run:

#### Each Schedule rule parameters

Following the TikTok Integration updates

7 days 30 days Following the Facebook Integration updates

7 days 30 days

#### Merge Module Integration schedule

The Schedule rules given above form this schedule, accurately following each source Integration's updates and not re-collecting unnecessary amount of data:

All those Schedule rules will make this statistics update cycle:

## Conclusion and next steps

Now we have your MM Integration:

- created, its data flow is set up
- filled with data from two source Integrations, data transformed
- the data's relevance is also ensured

This MM Integration is fully prepared for its statistics to be visualized with our Dashboard widgets.