Tag Archive

Tag Archives for " drip quick tip "

Salutation Formatting For Nameless Subscribers

It’s a common use case: You want to personalize someone’s email by using their first name. You may try to use a liquid snippet like this:

Hey {{ subscriber.first_name | default: "" }},

But there’s a problem. If the first name isn’t set, you end up with this wonky salutation with an awkward space:

Hey ,

How to Fix This:

There’s a bit of liquid syntax that isn’t well documented, if you add a hyphen to your brackets, Liquid will strip the newlines around the tag:

Hey {{- subscriber.first_name | default: "" -}},

This also works with logic tags which would look like this:

 {%-  -%}

Want more? 

Check out some other Drip Quick Tips. If you get your subscriber’s first & last name as a single text field,  here’s a workflow that splits first and last names.

How to Trigger a Workflow For Every New Subscriber In Drip

There’s a weird gap in Drip’s functionality: You can’t trigger a workflow or automation rule for all new subscribers. You can trigger rules based on “Submitted a form,” but that doesn’t work for users that are created via import or API. Here’s how you can work around that:

Drip Doesn’t Have A Trigger, But Zapier Does

Zapier has the “new subscriber trigger” that Drip is missing.

You can use Drip to trigger Zapier to trigger Drip. Weird I know.  For part two fo the zap, you can either add a tag to a subscriber or trigger an event. From there you can use Drip’s regular rules and workflows for all new subscribers.

How to Increment a Custom Field In Drip

Let’s say you want to keep count of how many times a user performs a certain action in Drip, how can you do that?

Drip doesn’t support this feature natively, but it’s easy to implement. Here’s an example using a rule that counts the number of times a user completed a particular event:

Check out the value tag:

{{ products_created | default: 0 | plus:1 }}

We’re using the Liquid tags with filters in this example. Let’s break it down.

First, you set a variable:

{{ products_created }}

Of course, saying products_created = products_created isn’t very useful, so we want to use a filter to change the data that is output. In this case, we want to say:

products_created = products_created + 1

Which in liquid looks like this:

{{ products_created | plus: 1 }}

This would be fine if we always knew that products_created would be set. We can make this tag more robust by adding an additional filter to set a default to ‘0’ for those cases.

{{ products_created | default: 0 | plus: 1 }}

Using this snippet, you can increment fields in drip.

How to Use First Names With a Fall Back (Drip Quick Tip)

You probably have different methods of adding users to your list. Or maybe you are testing whether or not asking for a first name affects conversion rates. Either way, there are situations when you want to use the first name if you have it and have a fallback if you don’t. Here’s a quick code snippet you can use:


<code>{% unless subscriber.first_name == null %}Hi {{ subscriber.first_name }},{% else %}Heya,{% endunless %}

 


Shout out to Kai Davis for sharing this technique with me.

[content_upgrade cu_id=”374″]Get the bonus content: Marketing Automation Intro Pack[content_upgrade_button]Click Here[/content_upgrade_button][/content_upgrade]

How to Change the Confirmation Link Text in Your Drip Welcome Emails

If you are using Drip for your marketing automation, you might want to change the copy on the “Confirm Your Subscription” Link that gets sent when people fill out a form. This link is an important call-to-action, and this little piece of text can have a big impact on your subscription conversion rate. Drip doesn’t make it clear how to change this copy, but it is possible.

Continue reading