Keitaro Best Practices #6: Campaign and stream cloning, stream imports/exports, and campaign redirects

We continue to analyze the cool features of the tracker in our issue of Keitaro Best Practices. Today we will talk about the possibility of cloning, exporting/importing of streams, and the «Send to another campaign» action of a stream — this is a valuable tool that will help you save a lot of time when working with a large amount of data.

Let’s look at the Cloning tool first.


For what task do you use the Cloning tool?

You use it to make copies of your campaigns or streams while maintaining settings and content (no statistics). You do this by either:

marking the campaigns you want to copy

or marking the streams within a campaign you want to copy

After clicking on the «Clone» button, you have the opportunity to clone the selected resources.

The «Enable» button allows you to quickly enable the selected resources. The «Disable» button — respectively, turn them off.

Why use the Cloning tool?

When working in a team, you can create separate campaigns for each member by cloning the parent campaign. In addition, when cloning streams, they can be placed in separate campaigns, which speeds up data updates in previously cloned campaigns.

Let’s move on to the next tool.

Export/import streams

For what task do you use the Export/Import tool?

This tool allows you to upload campaign streams to an external resource (for example, your local PC) and later download them by importing a JSON file.

On the Campaigns tab, click on the three dots in the Additional Menu section.

Select Export Streams to export all campaign streams to a JSON file. If streams are to be loaded into a campaign, choose Import.

Why use the Export/Import tool?

The Export/Import tool is convenient to use when you want to transfer a campaign and its contents between Keitaro trackers without moving the entire database. You can create a list of favorite streams and export them to JSON files. After that, it is easy to import the streams to Keitaro on other servers.

Send to Campaign action

Now let’s look at an alternative option: Send to Campaign.

For what task do you use the Send to Campaign action?

This action will transfer a click from the current stream to a new campaign, saving all its tags and data from the parent campaign (which can have several levels).

The click moved into this stream will continue its journey in the new campaign, but you will see its record in two campaigns.

Tip: if you don’t want to count clicks in the parent campaign, just turn off click counting in the stream settings.

Why use the Send to Campaign action?

Redirecting clicks to other campaigns is a great way to set up a multi-level traffic funnel without creating a complex filter structure.

Example: You work in a team where each member sends several offers at once for different geo, and simultaneously, each of them uses a lot of creatives. If they are sending into a common parent campaign, then you need to catch clicks, which will be simultaneously checked by filters for geo, buyer name, offer name, creative element name, etc. In this case, it is necessary to correctly compose exceptions since many filters in one stream are checked either all at once or until the first match. In general, the more selection criteria you have, the more difficult it is to put together the required set of filters and their conditions.

In situations like this, the Send to Campaign action will help you. Using it, all you need to do is check the parent campaign by one or two parameters, for example, the buyer’s name and geo, or just geo and send traffic to the next child level, checking it by the name of the creo or offer. Such a multi-level funnel will allow you to keep accurate statistics for each user without overloading the overall campaign.

After reading this article, we hope that you know more about the functions of cloning, exporting/importing streams, and sending traffic to another campaign. This knowledge will undoubtedly make your work with the tracker even more convenient and efficient.

See you in the next release of Keitaro Best Practices. Good luck with your work!

Keitaro Team

Team to deliver fresh and quality content!

View all posts by Keitaro Team →