Optimizing third party tag insertion
A request for a page is received. A client-side executable code that is included in a plurality of content elements associated with the page is extracted. A single instance of the client-side executable code is injected at an optimized location of the page. The page that includes the single instance of the client-side executable code is provided.
1. A system, comprising:
a communication interface configured to receive a request for a page; and
a processor coupled to the communication interface and configured to:
extract from a plurality of content elements associated with the page a client-side executable code that is included in the plurality of content elements associated with the page, wherein the client-side executable code is associated with a same third party verification code common to the plurality of content elements;
inject a single instance of the client-side executable code at an optimized location of the page; and
provide, via the communication interface, the page that includes the single instance of the client-side executable code.
2. The system of claim 1 , wherein the system comprises a server.
3. The system of claim 1 , wherein the system comprises an edge server.
4. The system of claim 1 , wherein the processor is configured to detect a plurality of occurrences of the client-side executable code in the plurality of content elements associated with the page.
5. The system of claim 1 , wherein the optimized location comprises a head portion of the page.
6. The system of claim 1 , wherein the processor is configured to obtain via the communication interface the plurality of content elements associated with the page from a content server.
7. The system of claim 1 , wherein the processor is configured to dynamically determine an optimized content element that includes the client-side executable code.
8. The system of claim 7 , wherein the optimized content element is determined based at least in part on a content consumption metric associated with a user.
9. The system of claim 7 , wherein the optimized content element is determined based at least in part on previous user engagement with the optimized content element.
10. The system of claim 7 , wherein the optimized content element is determined based at least in part on a content consumption metric associated with the optimized content element.
11. The system of claim 7 , wherein the processor is configured to determine an optimized placement of the optimized content element within an optimized version of the page.
12. The system of claim 7 , wherein the optimized content element is based on testing of different versions of a particular content element.
13. A method, comprising:
receiving a request for a page;
extracting from a plurality of content elements associated with the page a client-side executable code that is included in the plurality of content elements associated with the page, wherein the client-side executable code is associated with a same third party verification code common to the plurality of content elements;
injecting a single instance of the client-side executable code at an optimized location of the page; and
providing the page that includes the single instance of the client-side executable code.
14. The method of claim 13 , further comprising detect a plurality of occurrences of the client-side executable code in the plurality of content elements associated with the page.
15. The method of claim 13 , wherein the optimized location comprises a head portion of the page.
16. The method of claim 13 , further comprising obtaining the plurality of content elements associated with the page from a content server.
17. The method of claim 13 , further comprising dynamically determining an optimized content element that includes the client-side executable code.
18. A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for:
receiving via a communication interface a request for a page;
extracting from a plurality of content elements associated with the page a client-side executable code that is included in the plurality of content elements associated with the page, wherein the client-side executable code is associated with a same third party verification code common to the plurality of content elements;
injecting a single instance of the client-side executable code at an optimized location of the page; and
providing the page that includes the single instance of the client-side executable code.