Create a project. Name it something like "linker" or "mycards".  Anything will do. Don't enable Analytics for the project. If you have an Analytics account and want to add Analytics tracking later, you can come back and do that. Let's keep it simple for now.

To get Dynamic Links set up:

1. Click on Grow in left margin. There's a lot of other stuff all over the page; ignore it.
2. Click on Dynamic Links under Grow
3. Click on Get Started
4. If you don't have your own domain, Google will create a subdomain of page.link for you. e.g. lampworks.page.link. If you want it under your own domain, you'll need to be able to create address records in DNS to point to firebase. If you know what that means, go for it.​​

Now, to create a dynamic link:

1. Click on New Dynamic Link. This will have several steps, numbered as follows
   1. Create your link. It will fill in the domain you chose, and you can add something meaningful, or just take the short, random suggestion.
   2. Enter the target URL and a description. This is where you want people to go when they click your link. It can be to your Amazon page, your own website, a StoryOrigin promotion. Anything you want.
   3. Behavior for iOS. Skip this. Just click Next.
   4. Behavior for Android. Also skip this.
   5. Campaign tracking, social tags and advanced options (optional). Expand the Social Tags section and fill in the preview image URL, the preview title, and  the preview description.
2. Click Create. You're done!

Wait, where did we get the preview image URL in step 1.5?
​
There are several sources. If you are participating in a promotion on StoryOrigin, you'll get a banner URL in your acceptance message. You should use the personal link that you get for the target URL in step 1.2 as well.  If you have an image, you can upload to a blog, or to a MailerLite campaign, or any other service that will serve the image to you. If you want to show the cover of your book, go to your book's Amazon page, right-click on the cover, and select Open Image in New Tab. Once the new tab opens, grab the URL from the browser's address bar. Other storage services are hit-and-miss. Box will give you a direct link to an image file, for instance, but Google Photos will not.
​
The other thing to be careful of is the image's size ratio. The ideal Twitter image is twice as wide as it is tall (a ratio of 2:1). If it's too wide or too tall, Twitter is likely to clip the image so people can't see the entire thing without clicking on it (which will lose you half your audience right there). You can find services on the web that will pad an image to a specified ratio, or you can open it in Photoshop or other photo editor and resize the canvas.

I hope this has been a help to you.
​

Several of our recent newsletters ran into the dreaded gmail clipping: '[Message clipped]  View entire message' part-way down the message. They didn't seem that long. I knew we didn't want our newsletters clipped, so I dug into it.

Google arbitrarily clips messages at 102KB, so this limit isn't due to the visual length of the message, but to the unseen baggage inside.

People aren't very likely to click on the view entire message, so anything below that might as well be invisible. 

What's lost is often your footer, which has your Unsubscribe links and other contact info. You might be considered not in compliance with anti-spam laws if you don't have a visible unsubscribe link. You might also lose the last few banners promoting giveaways, which means those organizers might not see the views and clicks that you've promised them, making it harder for you to get accepted on future promotions.

So I used the 'Show original' command in gmail to look at what was there. 

It wasn't pretty.

I used MailerLite to compose the email, dragging their building blocks to make sections, and then blocks for books and reviews and so on, to make an attractive and easily-navigated newsletter. I even put in a small survey to ask what people wanted to see.

The code was appalling. There were inline styles on every element instead of style declarations, duplicating verbose instructions over and over. They stuffed all the html and javascript for the survey in the email, even though the only thing the email displays is a link to the real survey in a web browser.

Worst of all, they pretty-printed it. Nicely indented html that packed tons of whitespace that served no purpose other than to run up the byte count. For whom?  Who's going to care enough to 'Show original' and look at their code? (Well, perverse and annoyed web engineers like me, but I digress.)

I ran it through an html compression which removes whitespace and needless characters, and the payload shrank from 132KB to 82KB. Just that ONE STEP of removing the blanks would have kept my newsletter from clipping.

I sent that to MailerLite with a suggestion that the just insert an html compression stage just before mailing, as a quick and easy fix for this. They said they would put it in the suggestion list.

So, if you're using MailerLite and you're running into clipping issues, I suggest that you write to them too, and ask for HTML compression. Point out how it hurts your deliverability. Add some weight to this suggestion.

So for my next newsletter I wrote the entire thing in HTML. Just some header levels and a simple stylesheet, and I had an email that came in at a tiny 18KB. It looked indistinguishable from the MailerLite version, which couldn't do the same job in 132KB. 

I'm only picking on MailerLite because I'm using them. I'm sure the formatting of the other tools is just as bloated.