I would think the use-case presented here is quite common for the community.
We have a situation as follows:
Wen we publish a post to a Company LinkedIn page, oftentimes,we wish to share the same post on behalf of our internal team members, on their LinkedIn prfile feeds, doing so via their connected HubSpot social channel, direclty to each team members personal LinkedIn profile. This all of course to best practice. Nothing hairy here yet.
The method we apply to the process is via the HubSpot Social section by ticking the box left of a past published post (see the image below) and we start the clone process (in list view vs calendar view):
A popout pane appears right of the screen, as you see in this image below with the clone of our initial post pre-created for us, identically, and as we require.
Notice (as indicated by #4 on the image below) the post includes a URL and our issues takes place, when a URL is included in the post copy (the URL is also our main objective of post - the CTA of the post that will lead users to the posts objective destination).
We then click the little plus on the bottom of the image, as indicated by #3 on the image below, in order to duplicate our cloned social post and we repeat this process the same # of times per resepctive team members we intend to share for:
Here's where the issues takes place. Once we click the plus sign to duplicate the first time, sometimes (but not always and hence this post and if anyone else can help who has also experienced this issue) the image uploaded in our origonal and cloned post is replaced with a default image that loads from the referrencing website URL, from the text in the post above, and this is the issue.
There is some anomoly because this issue does not happen every time we do this process and we arent able to isolate the cause as to the decision of when it does and does not swap out the uploaded image with the default image from the website URL. Perhaps its the team members vs company page that HubSpot is picking up?
If anyone can assist, this would be much appreciate and if this is a bug, @hubspot over to you for assistance and remedy please..
...read more