TheTrafficEstimatorServiceof the AdWords API retrieves traffic estimates for proposed or existingcampaigns, ad groups, and keywords, including estimated stats like:
All of your visitors will be category and keyword targeted that are delivered via full page pop unders or interstitial ads. 30 Day Guarantee All of the visitors you purchase are guaranteed to be delivered or you will receive a pro-rated refund. I need to generate unique and consecutive numbers (for use on an invoice), in a fast and reliable way. Currently use a Oracle sequence, but in some cases generated numbers are not consecutive because of exceptions that may occur. I thought a couple of solutions to manage this problem, but neither of they convincing me. What solution do you recommend? In the last 31 days, you’ve helped me generate 1,864,246 unique visitors and 4,764,739 pageviews. That’s not too shabby! Even at my level, I still haven’t tapped out as only 25.1% of my traffic is repeat visitors. Now, can you guess how much traffic I had during the beginning of the year?
You can simulate proposed campaignsand ad groupsby using different campaign criteria, network settings, daily budgets, andmax CPCs.
You can also retrieve traffic estimates for an existing campaign or ad group byproviding the correspondingcampaignId
and adGroupId
.
Google Analytics Made Easy: New Visitors vs. Returning Visitors October 4, 2016 July 3, 2019 DBS Interactive One of the most powerful tools in your digital tool belt is also one of the most complicated to understand.
When creating a new campaign and ad group, or when modifying existing campaigns,you can use the TrafficEstimatorService to estimate future traffic and helpyou decide whether your proposed keywords (and settings) are optimal.For example, if the chosen keywords result in a lower CTR, you may want toreconsider using the keyword.
You can also use the TrafficEstimatorService to obtain information similar tothe Plan your budget and get forecasts feature ofthe Google Ads Keyword Planner.
Additionally, you can use theTargetingIdeaService to getadditional keyword ideas for an ad group. Before implementing the new keywordideas, use the TrafficEstimatorService to get an estimate on how these newkeywords will perform. Check outGenerating Targeting Ideasfor additional information.
The primary input to the TrafficEstimatorService is theTrafficEstimatorSelector
.
To retrieve traffic estimates, you must either specify existing campaignsand ad groups, or configure proposed campaigns and ad groups by setting theCampaignEstimateRequest
andAdGroupEstimateRequest
.
Within AdGroupEstimateRequest
, you must also specify aKeywordEstimateRequest
for the keywords you want traffic estimates for.
The following sections step through an example of getting traffic estimates from theTrafficEstimatorService.
You'll need to build the TrafficEstimatorSelector
from the bottom up. Tocreate a full request, you should build the request in the following order:
KeywordEstimateRequest
AdGroupEstimateRequest
CampaignEstimateRequest
First, you need to build the KeywordEstimateRequest
. It's common to retrieveestimates for multiple keywords: Each keyword should have a correspondingKeywordEstimateRequest
.
The list of keywords you send to TrafficEstimatorService can contain what youalready have in your keyword taxonomy, or it can contain new keywords youretrieve from theTargetingIdeaService.
Next, build the AdGroupEstimateRequest
. Like the keywords list, you canestimate on multiple ad groups. This example estimates only for a single adgroup:
Next, build the CampaignEstimateRequest
To get more accurate results, youshould also set additional campaign criteria when building theCampaignEstimateRequest
, such as location and language. You can also specifyexisting campaign IDs and ad group IDs in the CampaignEstimateRequest
and AdGroupEstimateRequest
, which allows the service to load historicaldata.
Finally, configure the TrafficEstimatorSelector
. You can then send it throughthe get()
operation to retrieve the traffic estimates encapsulated in theTrafficEstimatorResult
object. You can request a list of campaign-level estimates segmented by platformusing theplatformEstimateRequested
property.
Each CampaignEstimateRequest
object in the selector generates acorrespondingCampaignEstimate
object in the TrafficEstimatorResult
. Similarly, eachAdGroupEstimateRequest
object will have a correspondingAdGroupEstimate
object in the result. If you requested campaign-level estimates segmented by platform,they'll be available through theplatformEstimates
property of the CampaignEstimate
object.
The most important and interesting result object is the correspondingKeywordEstimate
object within the AdGroupEstimate
. It contains the lower bound(min
)and upper bound(max
)of the traffic estimation(StatsEstimate
)for each keyword.
Bear in mind that the returned values are estimates, andare not a guarantee that actual performance will be within these bounds.
Note: When usingtest accounts,the TrafficEstimatorService returns dummy data.The API doesn't directly provide an estimated total conversion value like the Keyword Planner, but you can calculate one from the stats provided:
You can use the TrafficEstimatorService like you useEnter or upload a list of keywords to get forecasts in the Google Ads KeywordPlanner.
To use the TrafficEstimatorService for this, you need to specify either apre-existing campaign, or create a mock campaign, complete with ad groups andkeywords:
Keyword Planner | AdWords API |
---|---|
Enter Keywords | KeywordEstimateRequest |
Targeting - Location | Use the Location criterion in CampaignEstimateRequest.criteria |
Targeting - Language | Use the Language criterion in CampaignEstimateRequest.criteria |
Targeting - Network | CampaignEstimateRequest.networkSetting |
Date Range | Not Supported |
In the Keyword Planner, you can specify a daily budget and a bid amount.In the AdWords API, adailyBudget
is part of theCampaignEstimateRequest
,and the bid amount, called maxCpc
, can be set either in theAdGroupEstimateRequest
or theKeywordEstimateRequest
.These must be specified at request time; so even though they're on theResults screen of the Keyword Planner, they must beincluded as part of the request when using the API.
Each client library contains a complete code example in its Optimizationfolder:
댓글 영역