🔍
Bing Ads API Quarterly Call – February 2018 - YouTube
Channel: Microsoft Advertising
[11]
>> Hello, everyone.
[13]
Thank you all for
joining the Bing
[15]
Ads API quarterly webcast,
[17]
where we are happy to share
with you what's new and
[19]
upcoming in the Bing
Ads API product roadmap.
[22]
Our goal is to
make sure that you
[24]
walk away from this webcast with
[25]
a clear understanding
of the benefits
[27]
of our newly released features,
[29]
while giving you the resources
[30]
to support you with adoption.
[32]
Now, before introductions, I'll
[34]
briefly review
our webcast Console.
[36]
You'll see that it's
customizable on your side,
[39]
where you can click the
content widgets on your screen,
[41]
move them around,
and resize them.
[43]
You can expand your
slide area by clicking on
[46]
the maximize icon on
the top right of the slide area,
[49]
or by dragging
the bottom right corner.
[52]
We recommend, if you can,
[53]
to leave the widgets as they
are so you have the ability
[56]
to see all of the great
resources at the same time.
[59]
We are also providing
live captioning.
[61]
You can see the words
scrolling below.
[64]
And for Q and A, please
feel free to input
[66]
your questions in the left-hand
widget as you have them,
[69]
and we'll answer
as many as we can
[70]
at the end of the webcast.
[72]
You'll see a resource list
[74]
on the right side of the screen.
[75]
The presentation is
available to download,
[77]
as well as links to topics
that you'll find helpful.
[80]
Okay, last housekeeping item.
[83]
We would love your participation
in our survey at
[85]
the end of the webcast
so that we can
[87]
improve in any way possible.
[89]
Alright. I'd now like
to introduce you to
[92]
our amazing PMs who will be
[94]
presenting their features
to you today.
[96]
As for myself, my name is
[97]
Andrew Jenkins and
I will be your host.
[99]
I am a Business PM working on
[101]
the API Partner Business Team.
[103]
Sabeshan Iyer, is in charge of
[105]
our Bing Ads API product which
includes the Ad insights,
[109]
bulk, campaign management,
[112]
customer management and
billing, and reporting services.
[116]
Marianne Aubin is
our Accounts and
[119]
Billing PM focusing on sign in,
[121]
sign up, user, and
payments within Bing Ads.
[125]
We do also have our technical
[127]
account managers who
will be answering
[128]
your questions live via
[129]
the chat window
throughout the call today.
[131]
So, please be sure to
submit your questions.
[134]
We will also set aside 10
minutes at the end for Q and A.
[138]
Please note that as many of
our features discussed in
[142]
today's call are either an early
[144]
planning or pilot phases,
[146]
dates and information
are subject to change.
[149]
With that, let's
jump into our agenda.
[152]
Today, we'll be
covering API v12,
[155]
the TLS 1.2 Update,
[157]
MSA Migration, and
Multi-User Support.
[161]
I will now turn it
over to Sabeshan,
[164]
where he will kick
things off with API v12.
[166]
>> Thanks for the intro, Andrew.
[169]
We're excited to announce
the next version of
[171]
the API v12 is coming soon.
[174]
This release will include
[176]
new endpoints for
all Bing Ads API services.
[179]
So, this includes add insight,
bulk, campaign management,
[182]
customer billing, customer
[184]
management, and
reporting services.
[186]
The main focus of
this release is
[188]
in the customer management area.
[190]
We're introducing support
for multi-user access,
[193]
which will allow you to access
[195]
different customer shells using
[196]
a single set of credentials.
[198]
More details on this feature
[200]
will be covered in
the following sections.
[202]
We're also introducing
the ability
[204]
to create accounts via the API.
[206]
This will simplify the workflow
for customers who have
[209]
a need to create lots of
[210]
accounts to support
their use cases.
[212]
Another useful feature
we're introducing is
[215]
the ability to pass time zone
in order for requests.
[219]
This will be helpful
to customers who
[222]
manage accounts based
in different time zones.
[224]
And then, some key breaking
changes we're introducing,
[227]
the retail release R. We're
[230]
ending support for the old
[231]
username and
password credentials,
[233]
and we'll only support the
Microsoft account credentials.
[235]
The only supported way for
[237]
authentication
will be via OAuth.
[239]
We're also requiring
a specification of
[242]
full address in account data
object for all countries.
[247]
In terms of timeline,
[250]
we will release
interface changes to
[252]
Sandbox in early March.
[254]
Please note that in most cases,
[256]
only updated interfaces may
be made available at first,
[259]
and then the backing logic
[260]
will be released a little later.
[262]
This is to allow
you some more time
[263]
to code for
the interface changes.
[265]
Please also note
that while we're
[267]
going to do our best effort to
[269]
keep the interface
changes constant,
[271]
in some cases, we
might change them in
[272]
Sandbox before we actually GA.
[275]
The global release of
[277]
API v12 will be in
Q2 of calendar year.
[280]
The exact dates
will be announced
[282]
on our blog the closer we
get to the actual release.
[284]
Also, once the API v12
is released,
[287]
API v11 will be deprecated and
[290]
will sunset by Q4
of calendar year.
[292]
Please make sure to prioritize
[294]
migrating API v12 as
soon as it's released.
[297]
Once again, we'll announce
the exact dates for
[299]
the sunset the closer we
get to API v12 release.
[303]
And then up next,
[304]
I'll be talking about
the mandatory update to TLS.
[309]
So, we're actually updating to
[313]
the latest version of
[314]
the transport layer
security protocol,
[316]
or TLS 1.2 by the end of March.
[319]
The reason we are doing
that is to provide
[321]
greater security
to communications,
[323]
to the Bing Ads systems.
[324]
We require all customers
to switch to
[327]
TLS 1.2 before the time
[330]
to have continued
access to the API.
[332]
If you're using Python,
[334]
you'll need to install
version 2.7.9 or above,
[338]
if you're using Python 2.0,
[340]
or version 3.4 or above,
[343]
if you're using Python 3.0.
[344]
If you're using Java,
[346]
you'll need to install
Java 1.7 or above.
[348]
If you're in .NET,
you'll need to
[350]
update to version 4.6 or above,
[352]
or if you need to
stay on version 4.5,
[355]
you'll need to include a line
of code that's mentioned
[358]
here in order to
hardcode to TLS 1.2.
[360]
And then finally,
if you're using PHP,
[362]
you'll need to confirm that
[364]
you're not hardcoded to use
an older version of TLS.
[368]
Please note that this is
a company-wide effort,
[371]
so unfortunately,
[372]
we're not able to
provide any extensions
[373]
or change the update deadline,
[375]
so we really
appreciate your help
[377]
in getting updated to
the latest version of TLS.
[380]
And if you have any questions,
[381]
always feel free
to reach out to us.
[383]
Next up is Marianne
who'll talk us through
[386]
our plans for MSA Migration.
On to you, Marianne.
[388]
>> Thanks, Sabeshan. And thanks,
[391]
Andrew, for the
introduction as well.
[393]
The first thing I'll be
talking about is MSA Migration.
[397]
You may have heard about
this already as it has
[399]
been in the works for around
the last four or so years.
[402]
Bing Ads have been migrating
[404]
from managed credentials to MSA,
[405]
which are Microsoft
account credentials.
[407]
MSA offers even
better security and
[410]
a single sign in for all your
[411]
Microsoft products and services.
[413]
This includes Bing Ads,
[414]
OneDrive, Skype, and Xbox.
[416]
Few users still use
managed credentials,
[418]
so we do hope that this will
be a low point of friction.
[421]
We will aim to sunset all
[424]
managed credentials across
[425]
all Bing Ads entry
points in 2018.
[428]
To this end, we do
encourage you to engage in
[430]
this migration proactively
so that you are ready.
[434]
In API v12, managed credentials
[437]
will no longer be supported
to access the API.
[440]
When a user tries to access
[441]
the API using
managed credentials,
[443]
we will return an error message
[445]
that this is no
longer supported.
[446]
Before adopting v12,
you will need to be
[449]
sure that all of your credentials
are using MSA accounts.
[452]
So, that's about it
for MSA Migration.
[456]
On a more exciting note,
[457]
I'll also be presenting on
[458]
a new feature called
Multi-User Access.
[460]
This GA-ed for
the Bing Ads Web UI and
[463]
Bing Ads Editor on January 22nd.
[466]
With Multi-User Access, you
can use one email address
[469]
and password to access
[471]
all your Bing Ads customers
and their accounts.
[473]
We've found that many users
[475]
have set up
multiple credentials,
[476]
to access their various Bing
Ads customers and accounts.
[480]
Now, with multi-user, you can
[482]
manage one email and
password for all accounts.
[484]
This means, there's
no more need to
[486]
manage multiple email addresses
and passwords anymore.
[489]
You can switch between
these customers with ease,
[491]
so you can go from one
customer's accounts to another,
[493]
or from one email address
and password combination.
[496]
You can finally also add
customers at any time.
[500]
So, when you're
invited to access
[501]
a new customer's account,
[503]
you can use your existing
email address and password.
[505]
All right, so I'll
just go through a quick
[508]
conceptual walk-through of how
[510]
this feature works
for four users.
[512]
So, in this example,
we have users one, two,
[514]
three, and [email protected].
[517]
And you can see,
[518]
they also have access to
[519]
different customers:
customers A,
[521]
B, and C under different roles
such as Viewer,
[524]
Super Admin, and Standard User.
[525]
With multi-user, the only
two users that could not be
[528]
merged together are
users two and four,
[531]
as they both have access
to the same customer.
[533]
However, customers two and
[536]
three can be consolidated
under user one.
[539]
And now, once you
consolidate these together,
[544]
user one now has access
to customers A, B,
[548]
and C, and they can use
[550]
the same roles as users two
and three previously had.
[555]
The next change that happens
with this is that user
[557]
two and three can now no longer
[559]
log in with those
email address and
[562]
password combinations that
they would use previously.
[564]
They have to use user:
[email protected] and
[567]
the corresponding
password to log
[569]
into all of their
customers and accounts.
[572]
So, what does this
mean for the API?
[575]
In v11, multi-user will
not lead to any changes.
[578]
Each of these access tokens
will continue to represent
[581]
permissions limited to
the corresponding user and role.
[585]
Starting with v12,
the access token for
[588]
a multi-user will represent
[589]
submissions to the
consolidated list of accounts.
[592]
So, you'll be able to
reap the full benefits
[594]
of multi-user from
within the API.
[596]
And there is
some extra documentation
[598]
here that you can
look at if you wish.
[600]
So, that's about
it for multi-user.
[602]
And back to you, Andrew.
[604]
>> Thanks, Marianne.
[606]
And thanks to both of you
for sharing the latest
[607]
from the Bing Ads API roadmap.
[610]
Let's briefly
pause on this slide
[612]
to highlight
the timeline discussed.
[614]
API v12 release will be
in Q2 calendar year 2018.
[619]
The switch to TLS 1.2 is
starting April 1st 2018.
[624]
API v11 will sunset in
Q4 calendar year 2018.
[629]
And lastly, the migration
to MSA will be in 2018.
[633]
Again, noting that
before adopting v12,
[635]
all of your credentials will
need to use MSA accounts.
[639]
Okay, let's now
transition to Q and A.
[642]
Give us just a moment to pull
these questions together.
[650]
Great. So, let's get
into our first question.
[657]
So, the first question
I see here is,
[660]
will v11 Sunset
beearly or late Q4?
[664]
Sabeshan, could you help
us to answer that one?
[666]
>> Yes. So, API v11 will
be some set early Q4,
[672]
just similar to how we
did this and set for
[674]
the previous version last year.
[678]
>> Great. And there are
a couple more questions,
[683]
and they are API v12 related.
[686]
So first, are there
any updates to
[690]
the customer APIs
or Ad Insights API?
[693]
Sabeshan, if you wouldn't
mind answering that as well.
[695]
>> Sure. Yes. There are
[698]
actually updates to
all the services.
[699]
As I mentioned previously,
[702]
there's changes in lots
[706]
of numerous changes
across all the services.
[709]
We'll definitely
have a full list of
[711]
updates and code improvements
closer to the release date,
[715]
but definitely yes, those
services also covered by v12.
[720]
>> We're good. All right.
[723]
And questions are
continuing to come in.
[726]
Take a sip of water. The next
question is again, API v12.
[730]
So, will there be a white list
for API v12 migration?
[733]
>> Actually, at this time,
[736]
we don't have any kind
of plans to do that.
[739]
So, we strongly recommend
all customers to
[742]
migrate to API v12 as
soon as we release it,
[745]
and as soon as it's
possible for them.
[746]
Just so that you
are not caught into
[749]
like big season when you're
busy with other stuff,
[751]
and you're not able to
catch up with migration,
[753]
so the sooner the better.
[755]
>> Okay.
[761]
Very good. See here.
[769]
All right. Just clicking
through some of the questions
[774]
that we're getting, okay.
[780]
So, the next question is,
[783]
what if we're targeting
.NET framework for Play Now?
[786]
What changes need to be made
for the TLS 1.2 Upgrade?
[790]
>> In that case,
[792]
we recommend that you agree to
[inaudible] version 4.6 or above,
[798]
because 4.6 is definitely
[800]
like an older version
of the same,
[804]
or which wouldn't support 1.2.
[805]
So yes, get an upgrade.
[809]
>> Okay, and I'll
ask this question,
[816]
and if we have to follow up with
[817]
the individual we can do that.
[819]
But do we know whether there are
[822]
plans to release a quick
level report with MS click ID,
[825]
Campaign ID, et cetera,
[827]
some of the Adwords click
performance with GCL IDs.
[832]
>> Not that I'm aware of.
[834]
We've heard this
asked once in a while.
[838]
So, what we would recommend
[839]
is definitely
please to go ahead,
[841]
and go to a user voice website,
[843]
and submit your Ads,
[845]
or for existing Ads,
[846]
please do add
your context to the ask,
[849]
and make sure that I
[851]
explain how this
benefit to work flows,
[854]
and you will be
happy to take a look.
[855]
And definitely, as always,
[857]
if we have any updates
running this in the future,
[860]
we'll be sharing it in
the feature quarterly court.
[863]
>> Great.
[867]
Okay. With that I think that
addresses all questions.
[872]
As you can see on the screen,
[875]
there are some additional
resources for you if
[876]
you'd like to do a bit
of additional digging.
[879]
Thank you all for joining
this Bing Ads API webcast.
[883]
We look forward to chatting
with you again soon.
Most Recent Videos:
You can go back to the homepage right here: Homepage