Your comments
Hi Ashley!
You definitely need a new GTM container for AMP - GTM actually requires it. (It is a choice when you set up the container, what type of container it is.)
Note that you'll have to set up GA and Chartbeat and whatever else you use in the new GTM account as well.
For now, the GTM AMP UA can be entered in the AMP settings panel. We will be moving it to a new software panel in the next few months though, when we go out of beta phase on this.
My understanding is that FB just uses your standard GTM and GA accounts for tracking. The issue is differentiating it from your regular traffic, and in that situation we created the tncms.page.platform dimension in GTM and GA to be able to identify it.
If you want to try this as best you can, then submit a ticket and we can look at it. Ask them to talk to me in the ticket and we can get you going! =)
Christine
Meagen, did you do this? It's amazing! Can I show it at the webinar tomorrow?
Hi Meagan!
Thanks for this! To be honest, this was my oversight when building the mosaic. When we first created it, the images didn't link anywhere at all. So I just asked that they go through to the image page so I could see them better. But, I should have asked for our image overlay behavior. It is better user experience, it has potential ad spots, and it more consistent. Better all around!
I will put in a change request. Thanks for the feedback!
Hey Kevin!
We're actually in the process of experimenting with this so we can document it with our full GTM launch.
Because Google AMP requires its own GTM container, you can just tell that container to create an AMP dimension for each page view.
For FBIA, you should be able to track tncms.page.platform = 'facebook instant articles'.
Like I said, this is still in test mode, but let me know if you need more explanation or help setting this up.
When an article with inline siblings is exported, those siblings become inline links back to the origin site (export/import is meant as a way of sharing data to non-syndicated sites). So, I don't think that will solve your issue even if you moved to that model.
Now, we've actually been talking about you a lot at TownNews.com. ;) We had a meeting the other day where we went over all of the possibilities to help improve your workflow. We had three ideas:
1. Total CMS Cloud - In alpha phase now.
2. Fast Syndication - The first step was added in our latest BLOX release (web services) and now we are going to build an internal mechanism so syndication uses those web services for a really fast response. We think it will be fast enough that you will be OK posting to TCMS first.
3. Hosted to TCMS Syndication - I can't remember if I've asked you about this before. Have you tried this? It may not have been available when you first were set up. Or is it not fast enough? You can still build things in hosted, but then when you need to, just export (through the Syndication channel) to print.
Let me know what you think! =)
Hey Chris, Have you looked at our webhooks feature?
In theory, if you have a service that is listening to a webhook, and then the webhook is notified every time a new asset is created or updated and it provides you a json payload with some basic information including the UUID.
Then, you can use the CRUD API to query for that asset's full information.
Also, when you syndicate an article with related links, there is an HTML link included in the destination story (which links back to the origin story). Again, a great way to gain SEO especially if used within the Content Exchange (or another group network).
I'd like to style those links... right now they are literally just an ahref, but we built them with a class so I could enhance them slightly. I think I will make them look like headline links. Let me know if anyone feels differently.
Hi Kyle!! I love to hear your feedback!
SIBLING ASSETS
So let's talk about sibling assets. I am convince-able - however, the purpose behind the siblings was to create more of the "related link" thing that you see at a lot of sites which I have had a lot of requests for. Here are some examples:
Washington Post
USA Today
CNN.com
So, that's what I was going for with the related siblings. Supposedly, these types of links (which are follow links) are very good for SEO and traffic to destination site (which may or may not be the current site). Then, you had the capability of switching to "summary" if you wanted a more robust sibling display.
I'd like to hear more from you or others about why you want this changed (I need some convincing). Maybe we need a mini-summary mode, plus the ability to set a default, like you said. That may be something we could look at...
OTHER TWEAKS
I do already have a feature request in already based on some late feedback (that we got either right before the release came out, or right after). Here is what I have on the slate for upcoming tweaks:
1. Make "headline link" font size the same size as the text, but bold. (On longform it is 4 points smaller than the body text.)
2. Siblings and parents in "summary" mode should be much shorter, with the preview floated to the left of the summary text. (See the story promo in this middle of this article: http://www.politico.com/story/2017/05/21/feinstein-scalded-by-anti-trump-fervor-238641).
3. Full-width children in "summary" mode should be side by side - preview left, story right, like summary on an index page, but larger than sibling, above. Right now children articles in full-width mode are HUGE.
3. Masthead photo should go below the "content discovery" feature on mobile/tablet. It is part of the story whereas Content Discovery is not.
4. Add some space below the "content discovery" feature - I recommend making it 40px instead of 20px - on tablet view (it's OK on mobile... on tablet it seems very close).
5. User reactions is too wide on longform. It should be the width of the tagline and other stuff at the bottom of the story.
6. By default, the sibling assets (which come in correctly as headline link), should be full width. (Right now they are floating right by default.) They should be link related link articles on CNN or other sites.
7. I also have a separate request for "better dark support" for pages where you want to create a dark background. I'll update the ticket with a link to an example of that.
8. Captions and cutlines should be standardized between inline displays, galleries and showcase/masthead (right now they are slightly different).
Hopefully all that will be done in 2 - 3 weeks.
There is a new webservices API available after our next update, which should be out tomorrow. Docs are available by going to your domain and adding /tncms/webservice. (Again, you'll see the new CRUD API after 1.35 is released).
Customer support service by UserEcho
