Adigami Blog

Digital Media Analytics

[adigami]

Adigami and Geckoboard

Adigami is now using the Geckoboard dashboarding platform to help clients visualize their online analytics data. We've had success with several clients and recently wrote about it on the Geckoboard blog. Check it out and let us know what you think.

[adigami]

We now support the SendGrid reporting API

In just a few weeks, we will begin to support the SendGrid e-mail marketing reporting API. This will be an important milestone for us since we already support ConstantContact and VerticalResponse and would like to round out our "e-mail package" with SendGrid.

A comprehensive online marketing plan needs to have an e-mail component and we're very pleased to be able to support a well-respected service such as SendGrid.

[adigami]

API for Display Advertising Reporting

Yesterday we released our reporting API for display advertising. We're very excited about supporting DART for Publishers and Yahoo! APT out of the gate with a few others to follow soon.

As you may know, Google has begun a slow migration of their DART for Publishers clients to the newer API which is called DoubleClick for Publishers. Adigami already supports the new system and we will be making some announcements around this API soon.

Our challenge with this work was to find a way to keep the simplicity of our API service without sacrificing power, and I think we achieved this goal! We believe you'll be very happy with the rich data and analysis we can provide for display advertising results.

[adigami]

REST API for Google Analytics

In our last post we showed how Adigami provides a powerful REST API for Google AdWords which doesn't have a REST API. We also support Google Analytics and want to showcase its features in this post.

Let’s continue our “Getting started…” blog series and see how you can easily set up access to a Google Analytics account and start to experiment with the API and the data.

We want to add your Analytics credentials for the client. But since Google Analytics has information about a site (or part of it), let's create the site on Adigami first. You'll see why we need to have a site defined for Adigami in step 3 and beyond.

NOTE: This post assumes you're using our API console on Apigee. If not, just build the URL's we're referring to by prepending https://sandbox.adigami.com to each one.

1. Click on the call that is labeled:

/clients/id/sites (POST)

You’ll need to provide just two parameters for this call: the site name and its URL (url).

Once you’re done setting these parameters, go ahead and POST the call. You'll get back a site object and can use the ID in the next call.

2. We're ready to add our Google Analytics credentials. Click on the call that is labeled:

/clients/id/credentials/source (POST)

You'll need to change {id} to your client's ID, and {source} needs to be set to the word analytics. This means your call will probably look something like this:

/clients/23/credentials/analytics (POST)

Finally, you'll need to define just 4 parameters for this call: email, password, profile_id, and site_id. You know what profile_id is in Google Analytics, and site_id refers to the site you just created on Adigami.

What happens next?

You should get a Credential object back that shows the information you provided but the password will be encrypted.

More importantly, Adigami will begin importing two weeks of data for this profile from Google Analytics. If you wait about a few minutes, you should be able to start looking at the data. 

3. One way to see if your data is coming in is to check the date range of available data for the site. Use the call labeled below and set the site {id} in the URL:

/sites/id/available-dates (GET)

Once you see some dates come back, you're ready to look at some numbers.

4. To see overall traffic results for the site, use the call labeled below and set the site {id} in the URL:

/sites/id/traffic/all (GET)

You should get something like this:

  { "new_visits": 6980, "pageviews": 21011, "bounce_rate": 0.640350042804147, "bounces": 6732, "entrances": 10513, "pages_per_visit": 1.99857319509179, "visits": 10513, "avg_time": 217.78150860839, "time_on_page": 2289537, "new_visit_rate": 0.663939883953201 }

This is a traffic summary for all the days that we have results for. If you want to limit the date range, simply set one or both of these parameters: start_date, end_date.

The format for dates is YYYY-MM-DD, e.g. 2011-09-26.

The next 3 calls allow you to dive into the traffic results and see performance by medium, by source, and by keyword. There's a lot more you can do beyond these calls and we will be posting more information about them.

4. To see performance by medium, click on the call labeled below, and set the site {id} in the URL:

/sites/id/traffic/mediums (GET)

5. To see just your paid traffic data, do this:

/sites/id/mediums/paid (GET)

6. To see performance of all keywords, do this:

/sites/id/traffic/keywords (GET)

Want more power?

Here're some other questions you can get answers to:

7. Which GA goals were completed on this site:

/sites/id/goals (GET)

8. What are the top 10 sites that referred traffic to this site:

/sites/id/traffic/sources?limit=10 (GET)

9. Since September 1, what are the top 3 social media sites that sent traffic to this site:

/sites/id/mediums/social?limit=3&start_date=2011-09-01 (GET)

Google Analytics is a powerful tool and provides a lot of data. What we've tried to do here is capture the 80% -- the most common needs that a user may have into a single easy to understand API so you can be up and running in minutes.

We are constantly improving and adding to our API. Please send us an email with your suggestions.

[adigami]

REST API for Google AdWords

One of the great things about the Adigami web analytics API is that it allows you to make REST calls and get data from a source that doesn't have a REST API -- like Google AdWords.

Let's continue our "Getting started..." blog series and see how you can easily set up access to a Google AdWords account for your new client and start seeing and playing with the data.

Remember that you had just created a new client, and know the ID that was assigned to it.

1. We want to add your AdWords credentials for the client. So, click on the call that is labeled:

/clients/id/credentials/adwords (POST)

You'll need to provide two or three parameters for this call depending on the type of AdWords account you have. For a regular (non-MCC) account, you'll just need:

    email, password

If you have an MCC account, add another parameter which describes the sub-account:

    clientEmail

Once you're done setting these parameters, go ahead and POST the call.

What happens next?

You should get a Credential object back that shows the information you provided but the password will be encrypted.

More importantly, Adigami has begun importing data from this AdWords account for the past two weeks. If you wait about 3-5 minutes, you should be able to start looking at the data. 

2. One way to see if your data is coming in is to check the list of campaigns under your client. Click on the call labeled:

/clients/id/campaigns (GET)

What you should get is a list of campaigns with some basic information about teach one.

3. To see the results for a given campaign, click on the call labeled below, and set the campaign {id} in the URL:

/campaigns/id/results (GET)

You should get something like this:

  { "cpc": 1.13350649350649, "cpm": 2.04570491034806, "roi": 0, "ctr": 0, "cost": 174.56, "impressions": 85330, "rank": 3.4, "clicks": 154, "cpa": 87.28, "conversions": 2, "revenue": 0 }

This is a performance summary for that campaign for all the days that we have results for. If you want to limit the date range, simple set one or both of these parameters:

  start_date end_date

The format for dates is YYYY-MM-DD, e.g. 2011-09-26.

What more can I get?

The next 4 calls allow you to dive into this campaign and see performance by adgroup, by creative, by keyword, and finally actions (or goals, or conversions).

4. To see performance by ad group, click on the call labeled below, and set the campaign {id} in the URL:

/campaigns/id/results/adgroup

5. To see performance by creative, click on the call labeled below, and set the campaign {id} in the URL:

/campaigns/id/results/creative

6. To see performance by keyword, click on the call labeled below, and set the campaign {id} in the URL:

/campaigns/id/results/keyword

7. To see performance by ad group, click on the call labeled below, and set the campaign {id} in the URL:

/campaigns/id/results/action

We hope this post showed you the power of our APIs and how easy it is to be up and running with Google AdWords results. You didn't have to learn the AdWords API, yet you saw some very powerful data aggregation in action. What's best is that if you also have a Microsoft adCenter account you can use this exact same API to get to get to that data. Next, we'll explore how you can setup Google Analytics and see some incredible traffic results with a very simple API in a matter of minutes. Stay tuned.

[adigami]

Getting started with the Adigami Web Analytics API

We're very happy to announce that our web analytics API is now publicly available in a sandbox environment that is hosted at Apigee. 

This note briefly describes the steps in getting started: First, email us and get an API key. Then, head over to our API console on Apigee and try out a few simple calls shown below. (If you want to do these tests in code, we'll have a blog entry soon that will point you to some sample code.)

A note about how data is organized in Adigami:

In Adigami, we have a simple hierarchy where your account is referred to as an agency, and your agency can have multiple clients. If you're going to monitor website traffic, then each client can have multiple sites attached to it.

We'll have a number of blog entries showing you examples on how to get data from all currently available data sources in Adigami. 

So, let's get started:

1. First, we need to set up the authentication:

Find the lock icon and select Custom Token from the menu:

Make the custom token settings as described in the image below:

OK, now you're ready to start making calls to the API.

2. This first call simply returns information about your account. Click on the call that is labeled:

/agencies (GET)

3. Let's add in your first "client". Remember that client is just a grouping terminology. You can think of it as a project, department, or indeed a client, depending on your application. Go ahead and click on the call that is labeled:

/agencies/id/clients (POST)

On the URL line, set the {id} parameter to the agency ID you got from the first call. We now have to set the parameter for this call which is just the name of the client. To do this, click on the cog wheel and fill out the parameter list as shown in the image below:

After you setup the parameter, just click Ok, and issue the command by clicking on the orange button that says POST. This should run without an error and return you some information about the newly added client.

4. Now let's make sure the client shows under this agency:

/agencies/id/clients (GET)

Our next blog entry will show you how to set up Google AdWords for your new client and see results in less than 5 minutes using very simple REST API calls we provide.

[adigami]

A unified API for web analytics

If you're building an app (for web or mobile) that needs to bring in data from a variety of data sources such as Google Analytics and AdWords, Microsoft adCenter, Facebook (social and ads), Twitter, DoubleClick (and others) then you'll need to learn the API's for each and every one of these sources AND continue to stay on top of the changes they make to them on a regular basis.

What does the Adigami API do? 

With the Adigami API what you get is a dozen or so standard calls that are applicable across many platforms. You will be up an running in a matter of minutes, your data is automatically kept up-to-date, and past data is stored for up to 1 year. We also keep track of any API changes and improvements that the data providers make so you can focus on what you need to do.

Web analytics is becoming a hot commodity as more and more companies scramble to gain a better understanding of their online advertising, inbound marketing, and online presence in general. We've spent a lot of time and effort in designing and developing the Adigami API and think that many others will find it useful in building their own apps. 

We're going to have a sandbox and some documentation ready over the next month and encourage you to try it for yourself.

How much does it cost?

Use of the sandbox will always be free, but we need to limit the amount of data that is captured in order control our costs. For now, we're planning to provide two weeks of data for any data source you add to your account. Email us if you're interested in getting an API key and let's start a conversation. We look forward to your feedback.

[adigami]

Support for Facebook data

Yesterday we released an update to Adigami that supports Facebook. What you get is both the social metrics such as likes, visits, etc. and Facebook Advertising data. You can tell Adigami which ad campaigns to track for you and they'll show up under the Display channel. We're very excited about this new functionality because Facebook is gaining a lot of momentum in its advertising and a lot of businesses are beginning to shift some of their spend to Facebook. Have a look at our work and tell us what you think.

[adigami]

It's time for "Push Analytics"

The problem with web analytics is not necessarily the volume or quality of the data. The problem is that it is rarely looked at by the people who should be paying attention. Adigami wants to solve this problem by pushing analytics to the user's website. We'll be posting more details on our plans shortly. Stay tuned.

[adigami]

Adigami 2.0 is live!

We just released the next generation of Adigami and updated our website. Have a look and let us know what you think. 

The new release incorporates a lot of the feedback we received from our earlier release and makes it super easy to track online marketing analytics for any site.