SanfordWhiteman

But the first click can't be known to be a bot click or human click.

As Dan says, this isn't about picking the master record when deduping on Email Address (or a custom compound dedupe key). Even if it the current master were elected at random that wouldn't be the worst thing in the world.It's about this quote from Support:a lead ID can be reused if a lead is deleted...

This is clearly a horrible P1 bug which should (if people cared as much as they should) require that the API be disabled for all users until it's fixed.The only way you can (sort of) sidestep this is by carefully offboarding everyone from your instance, tombstoning their records in your own database...

Like Stuart said, "without a naming convention to order them." The only reason yours appear to be grouped is that you use a naming convention.

Program member fields create multidimensional "lenses" you can use to view leads in the context of a program/campaign.Status is just one field per lead per program/campaign.

Yep, read Dan's post (and h/t to Dan for tipping me off to this years ago!).

But this would still mean (per standard Flow expectations) that they clicked the link at some point in the past, not necessarily in the event that fired the currently running trigger.I think it would end up being more surprising (and the current functionality is already surprising to many users).

This is already implemented, Dina. (At least as far as this Idea is concerned; as Dan points out, it needs expanded functionality to be useful to more people.)

"Cache our page headers" probably isn't what you mean. The caching HTTP headers (​Max-Age, ​ETag, If-None-Match, ​and related) on a main document don't apply to assets loaded within the document. Those assets need to have their own ​caching related headers: a main document with a far-future expiry w...

Like Devraj says, you can't mix up the order if you use Request Campaign, and the only thing that matters is if the same lead gets updated in the right order.It's true that you cant directly know when a whole batch is done. It this becomes a concern, you could use another field to manage the "batch ...