Publishers have created over 1.4B AMP documents that are hosted on over 750K unique domains. Such growth would have been impossible without strong support from over 100 third party tech companies that have already integrated with AMP.

If you are a technology provider for publishers or advertisers on the web, we invite you to add support to AMP so your customers can continue to leverage your technology and achieve our joint vision to build a better web.

There are 4 primary ways you can integrate with AMP:

1. Add your support to the amp-analytics extension

AMP analytics allows you to send events back to your server based on triggers configured by you. We have written an analytics integration guide to get you started.

If you simply need to add a tracking pixel with dynamic parameters to your tracking URL, check out amp-pixel. Be sure to document usage on your support pages for developers that may want to use your technology with AMP.

There are 20+ analytics providers who have added support to amp-analytics. Here is a sample pull request from the analytics provider Parse.ly.

2. Using an amp-ad extension

The amp-ad extension is reserved for serving display ads on AMP pages. Over 90 ad tech providers have added support to AMP. To get started, read the development overview or jump to developer instructions for adding your support to the amp-ad extension. Depending on the ad technology your company provides, you might find these integration instructions useful.

There are 90+ ad providers who have added support for advertising related features like amp-ad. Here is a sample pull request from the ad network Criteo.

3. Use the amp-call-tracking extension

If you provide call tracking measurement services, your use case may be supported with the new amp-call-tracking extension. This extension dynamically replaces a phone number in a hyperlink to enable call tracking, by executing a CORS request to substitute the number.

To learn more about how this extension might work for you, please see an AMP By Example or read about the documentation.

4. Adding a new extension/embed

If your use case cannot be accommodated by using amp-analytics, amp-pixel or amp-ad, please open a GitHub issue to discuss alternate options. We welcome new extensions that can be broadly used by a number of different companies. See the contributing extended components section for more details.

5. Using amp-iframe

Hold on – a 5th way?! There is indeed, but only as a last resort. If none of the above suit your needs, you could use the generic amp-iframe tag to allow publishers to embed your content, but this approach comes with a number of downsides, due to a few pitfalls related to performance and user experience that you can read about here.

Summary

To get started, please begin by reading our third party developer guidelines. The AMP project already supports a wide variety of third party use cases but we know that there are features of the web that are yet to be built.

For example, dynamic call tracking is a use case we don’t support in AMP yet but we are actively working with the community to add that support.

If you have questions or suggestions, please don't hesitate to file an issue or reach out on one of our discussion channels.

Additional resources