Required Minimum Functionality field conflicts

[Peter Kingswell]

Hi,

I'm updating our app to follow the AdWords RMF (https://developers.google.com/adwords/api/docs/requirements).  RMF R.20 states that ClickType must be shown.  This isn't possible for us since we have ReportDefinition.includeZeroImpressions set to true (which conflicts with ClickType).  Another conflict is that we download SearchBudgetLostImpressionShare and SearchRankLostImpressionShare, which also cannot be downloaded along with ClickType.  Here's the error message for the latter conflict:

Cannot select a combination of ClickType and AdvertiserExperimentId,AssistClicks,AssistClicksOverLastClicks,AssistImpressions,AssistImpressionsOverLastClicks,AverageFrequency,AveragePageviews,AverageTimeOnSite,AvgCallDurationSecs,BounceRate,Bounces,BudgetLostImpressionShare,CallDurationSecs,ClickAssistedConversionValue,ClickAssistedConversionValueLong,ClickAssistedConversionValueNonMoney,ClickAssistedConversions,ClickAssistedConversionsOverLastClickConversions,ClickReach,ContentBudgetLostImpressionShare,ContentImpressionShare,ContentLocalBidLostImpressions,ContentLocalShownImpressions,ContentLocalThrottledImpressions,ContentRankLostImpressionShare,CostPerEstimatedTotalConversion,EstimatedCrossDeviceConversions,EstimatedTotalConversionRate,EstimatedTotalConversionValue,EstimatedTotalConversionValuePerClick,EstimatedTotalConversionValuePerCost,EstimatedTotalConversions,EstimatedTotalConversionsManyPerClick,ExactMatchImpressionShare,ExternalAdChanges,ExternalBidChanges,ExternalBudgetChanges,ExternalChanges,ExternalKeywordChanges,ExternalNetworkChanges,ExternalStatusChanges,ExternalTargetingChanges,ImpressionAssistedConversionValue,ImpressionAssistedConversionValueLong,ImpressionAssistedConversionValueNonMoney,ImpressionAssistedConversions,ImpressionAssistedConversionsOverLastClickConversions,ImpressionReach,ImpressionShare,InternalAdChanges,InternalBidChanges,InternalBudgetChanges,InternalChanges,InternalKeywordChanges,InternalNetworkChanges,InternalStatusChanges,InternalTargetingChanges,LastClickConversions,LastClicks,NewVisitors,NumCalls,NumMissedCalls,NumReceivedCalls,Pageviews,PercentNewVisitors,QualityLostImpressionShare,ReachBucket,RelativeCtr,SearchBudgetLostImpressionShare,SearchExactMatchImpressionShare,SearchImpressionShare,SearchLocalBidLostImpressions,SearchLocalShownImpressions,SearchLocalThrottledImpressions,SearchRankLostImpressionShare,ValuePerEstimatedTotalConversion,VisitDuration,Visits

So it would seem to me that our options are:

- not download ClickType - and thus not entirely conform to the RMF

- not download the conflicting fields (e.g. SearchRankLostImpressionShare) - this would break important features in our app

- download the data twice - once for SearchRankLostImpressionShare and once for ClickType - obviously we want to avoid this (how would you merge the data?  sounds difficult)

Any advice appreciated!

Peter

[Peter Kingswell]

anyone? :)

[Anash P. Oommen (AdWords API Team)]

Hi Peter,

Our team doesn't deal with RMF compliance, so I cannot answer this question. Could you please reach out to the token review team by email? You should have an email they sent you during the token review or RMF compliance review process.

Cheers

Anash P. Oommen,

AdWords API Advisor.

On Tuesday, October 28, 2014 11:42:47 AM UTC-4, Peter Kingswell wrote: