Error Queries Sample Clauses

Error Queries a Query that is sent by Publisher to Yahoo! when a User enters an erroneous or incomplete URL in an Address Bar, clicks on an Erroneous Hypertext Link or enters a Keyword into an Address Bar.
AutoNDA by SimpleDocs
Error Queries. AOL may from time to time at its discretion send all or any portion of Error Queries received by AOL from AOL Users of the AFE AOL Properties to Google without editing, filtering, truncating or otherwise modifying such Error Queries, either individually or in the aggregate, unless otherwise permitted by the terms of this Seventh Amendment or the AFE Protocol. [****] To the extent Google declines to deliver AFE Ads pursuant to the preceding sentence, and in any other instance in which AOL elects not to send an Error Query to Google, AOL may at its option serve the error response page that is served in response to Error Queries as of the Effective Date, or any other page at AOL’s discretion. Without limiting the foregoing, (i) AOL will not submit a request for AFE Ads other than in response to Error Queries; (ii) AOL’s implementation will not prevent any valid domain name query from being routed to a Domain Name Server and to its intended destination IP address; and (iii) [****]. Google may update the AFE Protocol (the “Protocol Updates”) at any time in its sole discretion upon written notice to AOL (the “Update Notice”), and AOL may elect to comply with such Protocol Updates at its discretion. Notwithstanding the foregoing, if the Protocol Updates have been implemented by Google in order to implement technical changes that are reasonably necessary to Google’s implementation of the AFE Service, then provided that the Update Notices accompanying such Protocol Updates state such reasonable necessity, AOL shall be required to implement such Protocol Updates within [****] of receiving the Update Notice.
Error Queries. Customer shall send any and all Error Queries received by Customer from End Users of AFE Sites to Google in accordance with the requirements provided by Google, without editing, filtering, truncating, appending terms to or otherwise modifying such Error Queries, either individually or in the aggregate; and, notwithstanding anything to the contrary, Google will have no obligation to process requests for AFE Ads that are not sent in compliance with the requirements of this Agreement. Without limiting the foregoing, (i) Customer will not submit a request for AFE Ads other than in response to Error Queries; (ii) Customer’s implementation will not prevent any valid domain name query from being routed to a Domain Name Server and to its intended destination IP address; (iii) Customer may intercept Error Query traffic only through a Client Application installed on the End User’s computer and approved by Google in writing in advance (and not, for example, at the server level).

Related to Error Queries

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • User Information Any user or usage data or information collected via Station’s digital properties or related to Station’s digital properties, or any information collected from websites operated by Station’s affiliates under this Agreement, shall be the property of Station and/or such affiliates. Advertiser shall have no rights in such information by virtue of this Agreement.

  • Safeguarding Customer Information The Servicer has implemented and will maintain security measures designed to meet the objectives of the Interagency Guidelines Establishing Standards for Safeguarding Customer Information published in final form on February 1, 2001, 66 Fed. Reg. 8616 and the rules promulgated thereunder, as amended from time to time (the “Guidelines”). The Servicer shall promptly provide the Master Servicer, the Trustee and the NIMS Insurer information reasonably available to it regarding such security measures upon the reasonable request of the Master Servicer, the Trustee and the NIMS Insurer which information shall include, but not be limited to, any Statement on Auditing Standards (SAS) No. 70 report covering the Servicer’s operations, and any other audit reports, summaries of test results or equivalent measures taken by the Servicer with respect to its security measures to the extent reasonably necessary in order for the Seller to satisfy its obligations under the Guidelines.

  • BILLING ERRORS In case of errors or questions about electronic fund transfers from your share and share draft accounts or if you need more information about a transfer on the statement or receipt, telephone us at the following number or send us a written notice to the following address as soon as you can. We must hear from you no later than 60 days after we sent the FIRST statement on which the problem appears. Call us at:

  • Errors or Questions Call or write us, as explained in Section 23, as soon as you can if you think an error has occurred in your PayCard Account. We must allow you to report an error until 60 days after the earlier of the date you electronically access your account, if the error could be viewed in your electronic history, or the date we sent the FIRST written history on which the error appeared. You may request a written history of your transactions at any time by calling or writing us, as explained in Section 23. You will need to tell us: a. Your name and PayCard number. b. Why you believe there is an error and the dollar amount involved. c. Approximately when the error took place. If you tell us orally, we may require that you send us your complaint or question in writing within 10 business days. We will determine whether an error occurred within 10 business days of hearing from you and will correct any error promptly. If we need more time, however, we may take up to 45 days to investigate your complaint or question. If we decide to do this, we will credit your account within 10 business days for the amount you think is in error, so that you will have access to the money during the time it takes us to complete our investigation. If we ask you to put your complaint or question in writing and we do not receive it within 10 business days, we may not credit your account. For errors involving new PayCard Accounts or point-of-sale or international transactions, we may take up to 90 days to investigate your complaint or question. For new PayCard Accounts, we may take up to 20 business days to credit your PayCard Account for the amount you think is in error. We will tell you the results within three (3) business days of completing our investigation. If we decide that there was no error, we will send you a written explanation. You may ask for copies of the documents that we used in our investigation. If you need more information about our error-resolution procedures, call us, as explained in Section 23, or visit xxx.xxxxxx.xxx.

  • Errors, Questions, and Complaints a. In case of errors or questions about your transactions, you should as soon as possible contact us as set forth in Section 6 of the General Terms above. b. If you think your periodic statement for your account is incorrect or you need more information about a transaction listed in the periodic statement for your account, we must hear from you no later than sixty (60) days after we send you the applicable periodic statement for your account that identifies the error. You must: 1. Tell us your name; 2. Describe the error or the transaction in question, and explain as clearly as possible why you believe it is an error or why you need more information; and, 3. Tell us the dollar amount of the suspected error. c. If you tell us orally, we may require that you send your complaint in writing within ten (10) Business Days after your oral notification. Except as described below, we will determine whether an error occurred within ten (10) Business Days after you notify us of the error. We will tell you the results of our investigation within three (3) Business Days after we complete our investigation of the error, and will correct any error promptly. However, if we require more time to confirm the nature of your complaint or question, we reserve the right to take up to forty-five (45) days to complete our investigation. If we decide to do this, we will provisionally credit your Eligible Transaction Account within ten (10) Business Days for the amount you think is in error. If we ask you to submit your complaint or question in writing and we do not receive it within ten (10) Business Days, we may not provisionally credit your Eligible Transaction Account. If it is determined there was no error we will mail you a written explanation within three (3) Business Days after completion of our investigation. You may ask for copies of documents used in our investigation. We may revoke any provisional credit provided to you if we find an error did not occur.

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!