An event announced in three places, three days apart
Publishing from the CMS puts the same details everywhere at once, with the image already sized per platform.
Social Media Integration
Most businesses keep two versions of their news: the one on the website and the one on social, updated at different times by different people. Integration work makes one of them the source and lets the other follow.
That usually means the site publishes and the channels receive, because the website is the asset the business owns and the platform is the one it rents. Events, announcements, and new work go into the CMS once and syndicate out with the right image and the right link.
The reverse direction has its uses too. A feed of real posts or reviews on the site is worth more than a static testimonial block, provided it degrades gracefully when the platform's API changes, which it will.
// what you get
What's included.
- Publish-once workflow from the site's CMS out to the channels that matter
- Open Graph and Twitter card setup so a shared link renders as a designed card
- Feeds and review embeds on the site, cached so an API outage does not break a page
- Scheduling and queueing for announcements planned in advance
- Tracked links, so social traffic shows up separately in analytics
- Handover so the marketing person runs it without a developer
// where it fits
The situations this is usually bought for.
Links that share as a blank grey card
The first thing most people see of a site is a card in a text message. Getting the Open Graph set right is cheap and almost always neglected.
Reviews sitting on a platform, invisible on the site
Real recent reviews pulled onto the page, with a cached fallback so the section never renders empty.
// say hello
Tell us what you are trying to fix.
Discovery calls are free and usually last 30 minutes. We listen first, and we will tell you honestly if social media integration is the wrong thing to spend money on.
More in Web and commerce