Common use of Client Side Implementations Clause in Contracts

Client Side Implementations. For client side implementations (e.g., iFrame or Javascript data feed implementations), each AFC Request must contain an AFC Client ID provided and used as specified by Google. Upon Google’s receipt of an AFC Request as described above, Google shall transmit an AFC Results Set, to the extent available, via Google’s network interface in accordance with the AFC Protocol. Customer’s code shall, in each instance, ensure the display of the entire AFC Results Set that corresponds to such AFC Request in the manner contemplated by this Agreement, without editing, filtering, reordering, truncating, adding content to or otherwise modifying such AFC Results Set. Customer shall not send more than one (1) AFC Request per pageview unless otherwise authorized by Google.

Appears in 4 contracts

Sources: Google Products and Services Agreement (Clearwire Corp /DE), Google Products and Services Agreement (New Clearwire CORP), Google Products and Services Agreement (New Clearwire CORP)

Client Side Implementations. For client side implementations (e.g., iFrame or Javascript data feed implementations), each AFC Request must contain an AFC Client ID provided and used as specified by Google. Upon Google’s receipt of an AFC Request as described above, Google shall will transmit an AFC Results Set, to the extent available, via Google’s network interface in accordance with the AFC Protocol. Customer’s code shall, in each instance, ensure the display of the entire AFC Results Set that corresponds to such AFC Request in the manner contemplated by this Agreement, without editing, filtering, reordering, truncating, adding content to or otherwise modifying such AFC Results Set. Customer shall will not send more than one (1) AFC Request per pageview unless otherwise authorized by Google.

Appears in 4 contracts

Sources: Services Agreement (Infospace Inc), Services Agreement (Infospace Inc), Google Services Agreement (Answers CORP)

Client Side Implementations. For client side implementations (e.g., iFrame or Javascript data feed implementations), each AFC Request must contain an AFC Client ID provided and used as specified by Google. Upon Google’s receipt of an AFC Request as described above, Google shall will transmit an AFC Results Set, to the extent available, via Google’s network interface in accordance with the AFC Protocol. Customer’s code shall, in each instance, ensure the display of the entire AFC Results Set that (hat corresponds to such AFC Request in the manner contemplated by this Agreement, without editing, filtering, reordering, truncating, adding content to or otherwise modifying such AFC Results Set. Customer shall will not send more than one (1) AFC Request per pageview unless otherwise authorized by Google.

Appears in 2 contracts

Sources: Google Services Agreement (NameMedia, Inc.), Google Services Agreement (NameMedia, Inc.)