What happens when tags don't resolve? You might notice a lack of data or an unresolved tag at some point. Unresolved tags don't necessarily indicate a problem. Sometimes tags don't contain any data for that particular account. That's OK—data values can vary from account to account, or you might want more control over unexpected situations. This is where fall throughs come in handy.

Fall throughs are a tag function that allows you to specify an output if an initial tag fails to resolve. Simply add a double colon (::) at the end of a tag, followed by your desired outputs. You can stack multiple fall throughs and even incorporate tags within them. Let's explore a couple of examples.

Issue:

You use [new-inventory.price] to define your pricing. However, not all products have pricing included. In the image below, you can see that an error occurs in Tag Review: "No output. Check for unresolved or unclosed tags."

Solution:

As an alternative, you'd like to use the text "Call For Price" if the price isn't available. Let's look at how to use the double colon (::) to designate a fall through: [new-inventory.price::Call For Price]

Now we can see the successful output: Call For Price.

Issue:

You have inconsistent pricing tags across multiple accounts: price 1, price2, price 3. If price 1 fails, you'd like to use price2 and so on to ensure that the correct price is applied.

Solution:

As a solution, you stack fall throughs with the various tag values to ensure that the right value is used: [new-inventory.price1::[new-inventory.price2::[new-inventory.price3]]]

Note: The order of operations is key.