Thank you for the detailed explanations.
@Morgan_Jarvis Although we knew what C2C numbers were designed for, in our case, there was no real reason not to use them for all Google Ads assets. I could just insert them to all campaign types and couple them with Google tracking and all would work as expected.
Now there’s actually a solid reason to separate the C2C numbers from all Google Ads call extension numbers, because if we don’t we will either not be able to count some call conversion types (for example on desktop with Google tracking off), or count some twice (on mobile with Google on).
Since our particular use of CallRail C2C numbers was not by the book, this is more understandable. The other inconvenience here is that the C2C conversions are now going to be merged with all manual conversions CallRail is reporting to Google Ads (per @madelyn 's response to my question #2). Now, in order to use C2C functionality, we would have to use CallRail’s conversion action to count all CallRail conversion types, whereas previously we imported these from Analytics defined as 2 goals (1st time and repeat calls).
I can think of workarounds, but they are not very pretty: Import all conversions from CR (because they are all one feed), count them once, import repeat calls only from GA. Two sources will mean different way of timing the conversions, which will increase data inconsistencies.
So for our agency that’s 3 extra steps:
1- Create separate numbers for brand and product campaigns (added CR cost and effort) [EDIT: In fact, this is now unachievable as all CR numbers report to one conversion only]
2- Create new numbers for C2C and other Google Ads use, this time used as intended (added CR cost and effort)
3- Create new conversion types to value 1st and repeat calls separately (added effort and slight data inconsistency)
And all of this is to maintain our current setup across several clients, so there’s no real added value. That is why an opt-out button would be rather convenient.