I have lead sources coming in through several differetn API connections from several different partners. My question is this.
These leads are sorted to different saels teams based on the partner or offer. Originally i was using custom "lead source" picks for each partner, but from a scaleability standpoint that list would eventually get really huge, and unpleasant to work with.
My second thought was to have them send over the offer ID, All of our parnters have unique offer id's, and ahve a workflow assign it to campaign, then assign based on campaign. The problem wtih this one is that workflow fires after lead assignment rules.
I guess my high level question is this. Is it better to use Campaigns, or lead source for lead source tracking long term? The lead source seems like a rather generic field use to provide a general overview of all leads. Where campaigns offer better reporting and tracking options?
Thanks in advance.
1 件の回答
I would probably attempt to keep Lead Source as generic as possible. As you said, the more values in the picklist, the greater the administrative nightmare becomes.
When initially creating the leads, the campaign lookup field is available to populate. This field is no longer available once the lead is saved.
A common thing for web to lead forms is to pass the campaign record ID from the web page itself.
Passing this ID into the leads Campaign Lookup field lets you add the lead to the campaign straight away. You would be able to remove the workflow rules if you do this.
You should be able to populate this field from Web to Lead forms and API calls. You just need the campaign ID on the original source.
