Most content shared through ClearView Social is promotional or informational content: blog posts, industry news, announcements, etc. Sometimes, however, you'll be sharing content that actually drives a direct conversion: event signups, subscriptions to a newsletter, job referrals, or even direct sales. When you put links to such content into a Queue, adjust the content's URL to include URL Referral Fields before sending the Queue, so that successes may be properly attributed to the user that drove the conversion.
Edit URLs in Queued Items to add Referral Fields
When you’re in the Queue Builder, there’s now a little 🔗 icon you can use to edit the actual URL that lives behind a link.
Click this icon to bring up a window that allows you to edit the URL and add URL Referral Fields. Everything you're going to want to do almost certainly comes after the ? in the URL. A full discussion of the details of how URLs work is beyond the scope of this article, but the briefest possible summary is that you're going to want to either:
- If the URL already contains a ? and one or more parameter=value pairs, you'll want to tack &referralparameter=CLEARVIEW_FIELDNAME on to the end of those pairs. (The ampersand is important!)
- If the URL contains no ? and no parameter=value pairs, you're going to add ?referralparameter=CLEARVIEW_FIELDNAME on to the end of the URL. (No ampersand, and the question mark is important!)
The URL Referral Fields are
These three phrases, when included in the URL of a Queued Article, will be substituted with the individual details of each user receiving the queue. You can then listen for these on your site to credit conversions or signups to individual users.
The easiest way to test that you have used a URL Referral Field correctly is to Test Send the Queue to yourself, and then in the Queue Email you receive, click the Title of the Article to go visit the URL yourself (not the Share button). When you arrive at the Article in your browser, visibly inspect the URL—it should have substituted with your own first name, last name, or email accordingly. If you see your own data in the URL, you'll know it's working correctly; if you still see CLEARVIEW_FIELDNAME, you did something wrong, and ought to start a Support Chat to have us come take a look.
Capturing the Results on Your End
Capturing and listening to the field is your conversion software's responsibility. It will be up to your IT department or whoever administers and configures the particular system you are trying to attribute conversions inside. If you're passing over the field as, for example, user_source=CLEARVIEW_LNAME, then your IT department or software administrators are going to need to adjust the conversion page so that it listens for a field called user_source and expects it to contain the last name of an employee. ClearView Social Support is willing to assist with this and be an asset in explaining to people how to accomplish this, though at the end of the day it is not within our power to implement the solution for you—this part is inside your systems.
Let’s walk through an example together. Let’s say, hypothetically, I wanted my team to share links to my company’s own lead capture form… https://clearviewsocial.com/contact/. Now, it’s important to understand that if somebody just tweets a link—”Hey, everybody, sign up for our company newsletter! clearviewsocial.com/contact!”—then our web server, when traffic arrives at it, is going to have no idea who referred the traffic. All it can see is that a web browser showed up at it, asking for clearviewsocial.com/contact.
Instead, I’m going to write code on my signup form that listens for a field called referralsource and, if present, will note referralsource in the Contact record it creates when the form completes.
So, I’ll edit my ClearView Social Queued Article to substitute in the user’s information for referralsource, like so:
Now, when I send this queue to my whole team, the link Adrian Dayton shares will point to clearviewsocial.com/contact?referralsource=Adrian-Dayton and the link that Lindsey Ziccardi will share will be clearviewsocial.com/contact?referralsource=Lindsey-Ziccardi and so on. When our own blog server is processing the submission of the form, we’ll instruct it to save the value of referralsource just like it does the other form fields (name, company size, etc).