Feed and Social Publishing (Tracking Pixel)

In order to post an article content to a social channel, the canonical link of that article needs to be available in the content body. CMP clients who don’t use wordpress as their CMS but rather rely on feed publishing, need to be able to publish to a feed and any social channel from the CMP within a task. We introduced an API that receives the tracking pixel and the canonical link of the article, finds out which article it points to and accordingly update the article with the canonical link.

Once the article is updated, the CMP is made aware of this change, and if there are pending social publishes dependent on the article post, it proceeds with the publishing then.

 

Now there are a few ways to call this API from the client’s CMS site with the necessary data.

 

Tracking Pixel Log (deprecated after this feature release)

This solution is already in place for specific organizations. The way it works:

Step 1:

We need to add the CMS site’s url in our feed as a regex. So that our API knows which is the exact canonical link that should be saved in our content.

Screen_Shot_2017-11-30_at_4.47.35_PM.png


Step 2:

Next let’s add the content to a task and select a feed and social channel for publishing.

Screen_Shot_2017-11-30_at_4.48.26_PM.png

The content will be published to the feed channel while it keeps the social publishing pending until the article is updated with the canonical link.

 

Step 3:

We need to visit the page where our content is published in the CMS site. This will register the canonical link in our logs.

 

After the article receives the canonical link, the social publishing will move forward and should be successfully published to the selected channel.

 

There are quite a few dependencies for this to work -

  1. The user has to visit the publish article post at least once in order to register the canonical link
  2. Once the article is visited, the time taken to update the article can be at best around 15mins to more than 6 hours.
  3. The url pattern of the website where the client is publishing to needs to be saved as a regex in the CMP feed model
  4. If the client’s site strips the pixel from the article, there’s no way for this to work

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk