Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

Hi, You are only allowed to set the value of parallelTrackingEnabled attribute in test accounts and not in production accounts. To clarify, are you saying if you are passing

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

The issue is that in the c# library, parallelTrackingEnabled is set to be bool and is not nullable so you can not really assign null to that field. What's the workaround? On Friday, March 23, 2018 at 9:43:48 PM UTC+3, Matthew Wawrin wrote: > > Actually doesn't say these's the ability to opt-out

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

Actually doesn't say these's the ability to opt-out (I read it wrong... ), just the potential to opt-in early. We'll keep watching this post. It's cutting if very close between the roll-out of this feature and details on how we'll be able to control it both manually and through the API.

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

Thank you Milind, I'm aware of that guide on parallel tracking but it looks like it's been updated since my last visit and now says there will be the availability to opt out. Our tracking will break with this change. I'm looking forward to having API ability to opt-out as doing so manually

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

Hi Matthew, Please check the guide for more details about the Parallel tracking . If you haven't already, please keep an eye on our blogs

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

Hi Milind, Thank you for the reply, the change caught me and we're handling now. Are you able to expand on my question about what we'll be able to do with theparallelTrackingEnabled flag once this is rolled out to production accounts? Can this flag be used to turn on/off the behaviour at

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

Hi Matthew, As you are already doing, you will need to make sure that the parallelTrackingEnabled is set to null in the customer object to set the auto-tagging flag via