Making a copy of a code

What a duplicate carries over, what it deliberately does not, and when to use one.

What it is for

A second code set up the same way as one you already have. A per-table code for every table, a per-branch code for every branch, a second version of a campaign you want to measure separately — anything where the design and the settings are the same and only the destination or the label changes.

Press **Duplicate** on the code in the list. The copy opens in the editor straight away, because nobody duplicates a code in order to look at two similar rows.

What comes across

The destination, the content, the design, the placement label, the folder, the campaign, the UTM parameters, the routing rules and the gate — including its password. The routing rules and the gate are the laborious parts and are most of the reason to make a copy at all.

What does not

**The short address.** A copy gets its own, because the short address is what makes a code that code. The two symbols look different as a result, which is useful when you are testing two designs.

**The history.** The copy starts on zero scans, with no first-scan date and no alerts. A duplicate that opened on four thousand scans it never received would make every figure taken from it afterwards wrong.

Starting a code's figures again instead

If what you want is the same code with clean numbers — the usual reason being test scans before a launch — use **Clear data** rather than a duplicate. It empties the scan history and leaves the code, its short address and every printed copy exactly as they are.

It cannot be undone, and it destroys the events rather than hiding them. Export first if the figures matter.